We had several clients configured to communicate with this cluster of aero-speed nodes. Now that we have removed the configuration from all the clients we know about, there are still some read and write requests coming into this cluster, as shown in AMC.
I looked at the log file generated in /var/log/aerospike/aerospike.log, but could not get any information.
Update
The netstat command provided in the @kporter response shows the number of connections with the statuses ESTABLISHED, TIME_WAIT, CLOSE_WAIT, etc. But this does not mean that these connections are currently used for get / set operations. How to get the IP addresses from which aerospace operations are currently being conducted?
Update 2 (enabled)
As mentioned in the comments to @kporter's answer, the tcpdump command for the culprit client showed that packets that are still being sent to the aerospace cluster are no longer mentioned in the configuration file. This happened, although even the AMC of this cluster no longer showed TPS read / write.
Later I discovered that it stopped after restarting the service nginxon the client. Please note that the configuration file in the client now refers to the new aerospatic cluster, and the packets sent to this cluster do not stop after restarting nginx. It's weird, but it worked.
source
share