Detail
A client can observe that a batch transaction can either timeout or succeed past the set TotalTimeout. This perceived behavior depends on the client batch concurrency policy.Answer
By default Batch concurrency is set to false. This imply that a batch transaction is sent to each node of the cluster serially.In terms of a Totaltimeout the Actual TotalTimeout would be the product of the configured Batch client TotalTimeout and the number of nodes in the cluster.
Actual_TotalTimeout = TotalTimeout * NumberOfClusterNodes
For example if a client is sending a batch transaction to a 4 node Aerospike cluster and has a TotalTimeout policy of 7000ms, its possible for a batch job to timeout after 4 x 7000 = 28000ms.