mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-25 19:10:42 +00:00
9ac0aa7bba
This commit adds documentation for zero-token nodes and an explanation of how to use them to set up an arbiter DC to prevent a quorum loss in multi-DC deployments. The commit adds two documents: - The one in Architecture describes zero-token nodes. - The other in Cluster Management explains how to use them. We need separate documents because zero-token nodes may be used for other purposes in the future. In addition, the documents are cross-linked, and the link is added to the Create a ScyllaDB Cluster - Multi Data Centers (DC) document. Refs https://github.com/scylladb/scylladb/pull/19684 Fixes https://github.com/scylladb/scylladb/issues/20294 Closes scylladb/scylladb#21348
24 lines
1.0 KiB
ReStructuredText
24 lines
1.0 KiB
ReStructuredText
=========================
|
|
Zero-token Nodes
|
|
=========================
|
|
|
|
By default, all nodes in a cluster own a set of token ranges and are used to
|
|
replicate data. In certain circumstances, you may choose to add a node that
|
|
doesn't own any token. Such nodes are referred to as zero-token nodes. They
|
|
do not have a copy of the data but only participate in Raft quorum voting.
|
|
|
|
To configure a zero-token node, set the ``join_ring`` parameter to ``false``.
|
|
|
|
You can use zero-token nodes in multi-DC deployments to reduce the risk of
|
|
losing a quorum of nodes.
|
|
See :doc:`Preventing Quorum Loss in Symmetrical Multi-DC Clusters </operating-scylla/procedures/cluster-management/arbiter-dc>` for details.
|
|
|
|
Note that:
|
|
|
|
* Zero-token nodes are ignored by drivers, so there is no need to change
|
|
the load balancing policy on the clients after adding zero-token nodes
|
|
to the cluster.
|
|
* Zero-token nodes never store replicated data, so running ``nodetool rebuild``,
|
|
``nodetool repair``, and ``nodetool cleanup`` can be skipped as it does not
|
|
affect zero-token nodes.
|