FAQ How are connections created in async mode connection pools?
When using the Aerospike Java client, it is possible to specify a minimum number of connections per node (
asyncMinConnsPerNode) in order to prevent extra latencies while establishing new connections in case of sudden workload ramp up. How does the client go about creating these connections on startup for the async client?
When the clients start up there is a fixed number of 50 connections distributed over the configured event loops that are created in the first instance. When one connection is created another will start immediately afterwards until the defined value for
asyncMinConnsPerNode is reached.
The purpose of creating connections in this manner is to establish the pool (with the inital 50 connections) but not to overwhelm the cluster with connections requests, hence why connections are created one by one after the initial burst of 50.
- Refer to the How to Troubleshoot Async Delay Queue Full Errors article for useful information about event loop and delay queue behaviour.
JAVA ASYNC MINCONNSPERNODE CONNECTION CREATE