Problem Description
After following the Aerospike documentation on Quiescing a Node, there are still ops/sec for batch-index and reads. According to the documentation, batch and read operations shouldn’t be happening on the node shortly after it gets quiesced.Explanation
If migrations were occurring and not finished before quiescing a node, we could still see ops/sec for batch and reads. This is because the cluster is by definition not in a stable, settled state. Usually the replica partition should be able to take over as master right away, but if there were migrations ongoing before there could be subsets and duplicate resolution may occur. This is why operations could still likely happen on the node that was just quiesced.Solution
This is expected behavior. If you’re planning to take out the quiesced node, you can take it out as long as proxies aren’t happening to the quiesced node anymore. You can run the following commands in asadm to check the metrics for proxies to confirm if they’re still happening.
Admin > show statistics like from_proxy_read
Admin > show statistics like from_proxy_write
Admin > show statistics like from_proxy_batch_sub