Context
Deleting bins doesn’t delete the associated meta data. On Aerospike 6.x and earlier, this means that at some point the maximum limit for bin names would be breached. The following log entries would show up, indicating no more bin names can be added.
WARNING (bin): (bin.c::377) {test-namespace} bin-name quota full - can't add new bin-nameMethod
If possible, upgrade to Aerospike 7.x or later. If the cluster has to stay on Aerospike 6.4 or earlier, then follow this procedure:
-
Make sure the bin names(s) you want to delete have been removed from every record in the namespace. Even a single instance of a bin name will prevent the removal from working. This can be done through your client application, or through a scan using multi-ops or a UDF.
-
If secondary indexes are defined against a bin name to be removed, these must be deleted. Any remaining secondary indexes for the bin name will prevent the metadata from being removed. See asadm - Manage Secondary Indexes for more information.
-
Issue a cold restart on each node in a rolling fashion (waiting for migrations to complete before taking the next node down depends on the version, as the new cluster protocol introduced in version 3.13/3.14 does not require to wait for migrations to complete prior to taking the next node down).
Notes
- If running the Community Edition, the storage would have to be erased prior to bringing the node back (see further down).