We got a cluster with 3 nodes (2 at version 3.6.0 and 1 at version 3.6.1) with factor 2.
There was no migrations going on, so I decided to drop old indexes for sets which does not exists anymore.
After sending the drop command through AMC, Aerospike stopped respoding and clients startet to get timeouts.
AMC is showing that all nodes are down, and when trying to get a stat on the dropping process through AQL it return a “error: (9)” message.
The services are still running and there are no errors to see in the logs.
I also tried to restart one of the nodes, which failed and seems to be blocked by something (I can see in the log that it got the shutdown message “SIGTERM received, shutting down”). After this line the “INFO (drv_ssd)” line are just repeated in the logs with no changes in the values.
Should I just wait for it to finish? How do I see if it is working? Shouldn’t Aerospike be running while dropping?
Please let me know if I can get you further informations.
Thanks in regards