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
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3610,6 +3610,7 @@ The ``replication`` section defines configuration parameters related to :ref:`re
3610
3610
Additionally, instances without a persistent name are ignored.
3611
3611
3612
3612
If an instance is in read-write mode and has the latest database schema, it initiates the expulsion of instances that:
3613
+
3613
3614
- Match the specified prefix
3614
3615
- Absent from the updated YAML configuration
3615
3616
@@ -3618,7 +3619,7 @@ The ``replication`` section defines configuration parameters related to :ref:`re
3618
3619
The ``autoexpel`` logic is activated during specific events:
3619
3620
- **Startup**. When the cluster starts, ``autoexpel`` checks and removes instances not matching the updated configuration.
3620
3621
- **Reconfiguration**. When the YAML configuration is reloaded, ``autoexpel`` compares the current state to the updated configuration and performs necessary expulsions.
3621
-
- ``box.status`` **Watcher Event**. Changes detected by the ``box.status watcher`` also trigger the ``autoexpel`` mechanism.
3622
+
- ``box.status`` **Watcher event**. Changes detected by the ``box.status watcher`` also trigger the ``autoexpel`` mechanism.
3622
3623
3623
3624
New instances
3624
3625
@@ -3631,6 +3632,7 @@ The ``replication`` section defines configuration parameters related to :ref:`re
3631
3632
global levels. It is not applicable at the instance level.
3632
3633
3633
3634
Configuration fields
3635
+
3634
3636
- **`enabled`** *(boolean, default: `false`)*: enables or disables the ``autoexpel`` logic.
3635
3637
3636
3638
- **`by`** *(string, default: `nil`)*: specifies the ``autoexpel`` criterion. Currently, only `prefix` is supported and must be explicitly set.
@@ -3677,10 +3679,11 @@ The ``replication`` section defines configuration parameters related to :ref:`re
3677
3679
3678
3680
3679
3681
This configuration:
3682
+
3680
3683
- Sets up authentication with a guest user assigned the super role.
3681
-
- Enables the autoexpel option to automatically expel instances not present in the YAML file.
3682
-
- Defines instance names based on a prefix pattern: {{ replicaset_name }}.
3683
-
- Lists three instances: r-001-i-001, r-001-i-002, and r-001-i-003.
3684
+
- Enables the ``autoexpel`` option to automatically expel instances not present in the YAML file.
3685
+
- Defines instance names based on a prefix pattern: ``{{ replicaset_name }}``.
3686
+
- Lists three instances: ``r-001-i-001``, ``r-001-i-002``, and ``r-001-i-003``.
3684
3687
3685
3688
3686
3689
2. Open terminal window and start three instances using the following commands:
@@ -3713,8 +3716,7 @@ The ``replication`` section defines configuration parameters related to :ref:`re
3713
3716
3714
3717
4. For the leader instance (``r-001-i-001``), check the _cluster space:
3715
3718
3716
-
.. admonition:: Info
3717
-
:class: fact
3719
+
.. hint::
3718
3720
3719
3721
The ``_cluster`` system space in Tarantool stores metadata about all instances currently recognized as part of the cluster.
3720
3722
It shows which instances are registered and active.
0 commit comments