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 Paxos-single-replica-limit
What is paxos-single-replica-limit?
The paxos-single-replica-limit is a parameter within the service stanza that defines a minimum number of nodes in the cluster, at or below which replica records will not be stored. This means only master copies will be stored on the cluster.
What is the default value?
The default value for paxos-single-replica-limit is 1. This makes sense as there is no value to holding replica records in a single node cluster.
Can the parameter be set dynamically?
No, this is a static parameter and cannot be set with asinfo. It is unanimous meaning all nodes within the cluster must have the same value for the cluster to form. If an attempt is made to start a node where paxos-single-replica-limit is different to other nodes the behaviour is undefined. This implies that even if the node starts and joins the cluster it is not a safe or advisable procedure to attempt in a production environment.
Where might the parameter be set to a value greater than 0?
If a use case prioritised availability of new records and system resources are limited, it may not be desirable to wait until only 1 node remains before stopping storage of replicas.
Is paxos-single-replica-limit respected in a rack aware configuration?
Yes. Whether the nodes that go down are of the same group or different groups to the remaining nodes, the value for paxos-single-replica-limit will be respected.