FAQ - What are the unanimous configuration parameters


#1

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-protocol**    |
|                    || paxos-max-cluster-size*    |                      |
|--------------------++----------------------------+----------------------|
|  network.heartbeat || mode (mesh/multicast)      |  protocol**          |
|                    ||                            |                      |
|--------------------++----------------------------+----------------------|
|                    || single-bin                 |                      |
|                    || data-in-index              | set-delete***        |
|  namespace         || replication-factor         | set-disable-eviction |
|                    ||                            |                      |
|--------------------++----------------------------+----------------------|
|                    ||                            |                      |
|  security          ||  requires stopping app     |                      |
|                    ||  traffic.                  |                      |
|                    ||                            |                      |
|--------------------++----------------------------+----------------------|

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).

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

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

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

References

Changing replication-factor:

Changing heartbeat from v2 to v3:

Changing max cluster size:

Changing paxos-single-replica-limit:

Upgrading to the new cluster protocol:

Keywords

UNANIMOUS CONFIGURATION STATIC DYNAMIC

Timestamp

12/08/2017