If maxRetries is exceeded, the transaction will abort with AerospikeExceptionTimeout.
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 write: 0 (no retries)
Default for read: 2 (initial attempt + 2 retries = 3 attempts)
Default for scan/query: 5 (6 attempts. See ScanPolicy comments.)
public int maxRetries