Skip to content

Commit 820eef5

Browse files
committed
errors fixed
1 parent f67ce67 commit 820eef5

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

doc/reference/configuration/configuration_reference.rst

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3648,7 +3648,7 @@ replication.autoexpel_by.*
36483648
``replication.autoexpel_by`` purpose is to define the criterion used for determining which instances in a cluster are
36493649
subject to the ``autoexpel`` process.
36503650

3651-
The by field helps differentiate between:
3651+
The ``by`` field helps differentiate between:
36523652

36533653
- Instances that are part of the cluster and should adhere to the YAML configuration.
36543654
- Instances or tools (e.g., CDC tools) that use the replication channel but are not part of the cluster configuration.
@@ -3687,7 +3687,7 @@ replication.autoexpel_enabled.*
36873687

36883688
By default, the ``enabled`` field is set to ``false``, meaning the ``autoexpel`` logic is turned off. This ensures that no instances are automatically removed unless explicitly configured.
36893689

3690-
Enabling ``autoexpel`` Logic
3690+
Enabling ``autoexpel`` logic
36913691

36923692
To enable ``autoexpel``, you should set enabled to true in the ``replication.autoexpel`` section of your YAML configuration:
36933693

@@ -3775,7 +3775,8 @@ replication.autoexpel_prefix.*
37753775
37763776

37773777

3778-
**Full Example**
3778+
Full example
3779+
~~~~~~~~~~~~~
37793780

37803781
1. Create a ``config.yaml`` file with the following content:
37813782

0 commit comments

Comments
 (0)