FAQ - What are the unanimous configuration parameters

The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.

FAQ - What are unanimous configuration parameters

Configuration parameters that are classified as unanimous must be the same across all nodes in a cluster.

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-delete[3]
set-disable-eviction
security To assess which version of Aerospike
requires bringing down the entire cluster,
refer to the following FAQ4.

Notes

  • Prior to the new cluster protocol introduced in versions 3.13/3.14, adding/removing namespace requires a full cluster restart (full shutdown and restart).

  • 1 paxos-max-cluster-size is deprecated as of hb protocol v3 (3.10/3.14).

  • 2requires special extension of heartbeat timeout and interval prior to dynamically changing.

  • 3 set-delete is deprecated by truncate command since 3.12.

  • 4 FAQ - Is a cluster shutdown required to enable Aerospike security.

References

Keywords

UNANIMOUS CONFIGURATION STATIC DYNAMIC

Timestamp

September 2019