Context
When adding a new node to a cluster using security, it is best practice to copy the existing security.smd file from one of the active nodes in the cluster to the new node before adding the new node to the cluster. This is suggested because we can run into an edge case where we get role violations from all nodes in the cluster until a fresh login or client applications are restarted.
Method
-
Copy the security.smd file from an active node in the cluster to the new node.
-
Add the new node to the cluster.
-
When migrating SMD files, best practices dictate that this is tested thoroughly in a test environment, before implementing in production systems.
Notes
Error that we can run into on the Aerospike server side:
WARNING (security): (security.c:5129) delete role - role not in user