NOTICE: This version has a major bug if the BatchPolicy.DirectGetThreshold
is set to values larger than 0. Update to v4.6.1 if you are using Batch commands.
We recommend testing your app vigorously before deploying this version if you depend on batch requests.
-
New Features
- [CLIENT-2238] Convert batch calls with just a few keys per node in sub-batches to sequential Get requests. If the number keys for a sub-batch to a node is equal or less then the value set in
BatchPolicy.DirectGetThreshold
, the client use direct get instead of batch commands to reduce the load/latency on the server. - [CLIENT-2240] Add more client statistics.
- Adds the following statistics:
circuit-breaker-hits
: Number of times circuit breaker was hitconnections-error-other
: Connection errors other than timeoutsconnections-error-timeout
: Connection Timeout errorsconnections-idle-dropped
: The connection was idle and droppedconnections-pool-overflow
: The command offered the connection to the pool, but the pool was full and the connection was closedexceeded-max-retries
: Number of transactions where exceeded maximum number of retries specified in the policyexceeded-total-timeout
: Number of transactions that exceeded the specified total timeouttotal-nodes
: Total number of nodes in the cluster
- Adds the following statistics:
- [CLIENT-2238] Convert batch calls with just a few keys per node in sub-batches to sequential Get requests. If the number keys for a sub-batch to a node is equal or less then the value set in