I have attempted to delete a set at runtime following the instructions outlined here a couple of times, but unfortunately in both cases it didn’t go so well.
The first time, after a few seconds of a huge burst in writes, during which the application requests were all timeouted, the write TPS returned to normal. After running
show sets in aql, I noticed there were still objects in the set and the set itself was still marked to be deleted (
set-detete = true). The set remained in this state no matter how much time passed, even though running
select * for the set returned 0 rows.
Even worse, the second time I tried this (on a different set), all the servers in the cluster failed during the same burst write period.
I wanted to ask if there is any throttling mechanism for the deletion so that it doesn’t use up all the cluster resources? Are there maybe plans for such a feature?
Another concern is that after restarting the servers on the second case, the aql
select * command for any set returns
Error: (11) AEROSPIKE_ERR_CLUSTER, even though other aql commands like
show sets seem to work fine and the amc console reports all reads and writes as successful.
I am running aerospike v3.4.0.