If maxRetries is exceeded, the transaction will abort with AerospikeException Timeout.
WARNING: Database writes that are not idempotent (such as Add()) should not be retried because the write operation may be performed multiple times if the client timed out previous transaction attempts. It's important to use a distinct WritePolicy for non-idempotent writes which sets maxRetries = 0;
Default for read: 2 (initial attempt + 2 retries = 3 attempts)
Default for write: 0 (no retries)
Default for partition scan or query with null filter: 5 (6 attempts. See ScanPolicy comments.)
No default for legacy scan/query. No retries are allowed for these commands.
Assembly: AerospikeClient (in AerospikeClient.dll) Version: 3.9.8.0 (3.9.8)