You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/reference/configuration/configuration_reference.rst
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -933,9 +933,7 @@ The ``replication`` section defines configuration parameters related to :ref:`re
933
933
* ``config``: use the specified node to bootstrap a replica set.
934
934
To specify the bootstrap leader, use the :ref:`<replicaset_name>.bootstrap_leader <configuration_reference_replicasets_name_bootstrap_leader>` option.
935
935
936
-
* ``supervised``: a bootstrap leader isn't chosen automatically but should be appointed using ``box.ctl.make_bootstrap_leader()`` on the desired node.
937
-
938
-
Configuration fails if no bootstrap leader is appointed during a :ref:`replication.connect_timeout <configuration_reference_replication_connect_timeout>`.
936
+
* ``supervised``: a bootstrap leader isn't chosen automatically but should be appointed using :ref:`box.ctl.make_bootstrap_leader() <box_ctl-make_bootstrap_leader>` on the desired node.
939
937
940
938
* ``legacy`` (deprecated since :doc:`2.11.0 </release/2.11.0>`): a node requires the :ref:`replication_connect_quorum <cfg_replication-replication_connect_quorum>` number of other nodes to be connected.
941
939
This option is added to keep the compatibility with the current versions of Cartridge and might be removed in the future.
Make the instance a bootstrap leader of a :ref:`replica set <replication-bootstrap>`.
11
+
To be able to choose the instance as a bootstrap leader manually, you need to set the :ref:`replication.bootstrap_strategy <configuration_reference_replication_bootstrap_strategy>` configuration option to ``supervised``.
12
+
13
+
When ``replication.bootstrap_strategy`` is set to ``supervised``, the instances do not choose a bootstrap leader automatically but wait for it to be appointed manually.
14
+
Configuration fails if no bootstrap leader is appointed during a :ref:`replication.connect_timeout <configuration_reference_replication_connect_timeout>`.
15
+
16
+
.. NOTE::
17
+
18
+
When a new instance joins the existing replica set with ``replication.bootstrap_strategy`` set to ``supervised``,
19
+
this replica doesn't choose the bootstrap leader automatically but joins to the instance on which
20
+
``box.ctl.make_bootstrap_leader()`` was executed last time.
0 commit comments