Detail
Configuration parameters that are classified as unanimous must be the same across all nodes in a cluster.
Answer
For static parameters, you must bring down the entire cluster, modify the aerospike.conf file and bring up the nodes one by one. You cannot use a rolling restart to change them.
For dynamic parameters, you will need to use asadm to run asinfo to apply on all the nodes but some may require special treatment (increasing of heartbeat timeout/interval for example).
This table summarize the configuration parameters that are unanimous:
| Context | Static | Dynamic |
| service | paxos-single-replica-limit paxos-max-cluster-size[1] | paxos-protocol[2] |
| network.heartbeat | mode (mesh/multicast) | protocol[2] |
| namespace | single-bin data-in-index replication-factor | set-disable-eviction replication-factor (only AP starting in version 6.0) |
| security | To assess which version of Aerospike requires bringing down the entire cluster, refer to notes section | |
Notes
- For Aerospike Server versions 4.6.0.2, 4.5.3.5 or earlier, 4.5.2.5 or earlier, 4.5.1.10 or earlier, 4.5.0.14 or earlier the
enable-securityparameter is static, meaning it requires a node restart and unanimous. -
2requires special extension of heartbeat timeout and interval prior to dynamically changing.