The sleep only occurs on connection errors and server timeouts which suggest a node is down and the cluster is reforming. The sleep does not occur when the client's socketTimeout expires.
This field is ignored in async mode.
Reads do not have to sleep when a node goes down because the cluster does not shut out reads during cluster reformation. The default for reads is zero.
Writes need to wait for the cluster to reform when a node goes down. Immediate write retries on node failure have been shown to consistently result in errors. The default for writes is 500ms. This default is implemented in ClientPolicy
Assembly: AerospikeClient (in AerospikeClient.dll) Version: 3.5.0.0 (3.5.0)