Detail
Few queries regarding the client open connections to the server:- Is there any way to track the open connections?
- What are the default open connection configurations?
- Will there be any performance hit with increasing number of connections?
- Can we restrict number of open connection per user when using LDAP?
Answer
1. Current client open connections can be tracked in aerospike logs with the following line :Feb 27 2024 08:10:21 GMT: INFO (info): (ticker.c:316) fds: proto (2,2,0) heartbeat (0,2,2) fabric (0,0,0)proto part includes client connections statistics, in order: client_connections, client_connections_opened, client_connections_closed
2. The maximum allowed open connections for the cluster globally can be defined in aerospike configuration file with parameter proto-fd-max . This parameter sets a default limit of 15k but within this the clients will use what they need and this value should be less than the maximum open files allowed at OS level.
3. No but increasing connection counts can indicate a client ‘thrashing’ to try and maintain throughput in the event of server latency. As long as there is not much of a connection churn, things should be fine even with higher connections which are less than the OS limit.
4. No, you cannot limit connection count from clients to aerospike database based on username. Connections can be limited from client side using the language’s max_connections settings and on server side globally per server, using proto_fd_max. User level restrictions will be applicable at OS level.