Skip to content

Commit e7fcf08

Browse files
alina-derkach-oazaalina-derkach-oaza
authored
PXC-5202 [DOCS] Remove variables from 9.7 (#329)
modified: docs/wsrep-system-index.md
1 parent 6656f75 commit e7fcf08

File tree

1 file changed

+3
-124
lines changed

1 file changed

+3
-124
lines changed

‎docs/wsrep-system-index.md‎

Lines changed: 3 additions & 124 deletions
Original file line numberDiff line numberDiff line change
@@ -116,8 +116,6 @@ For more information, see [PXC Strict Mode](strict-mode.md#percona-xtradb-cluste
116116
| Dynamic: | Yes |
117117
| Default Value: | ``ON`` |
118118

119-
As of Percona XtraDB Cluster 8.0.26-16, the ``wsrep_slave_FK_checks`` variable is deprecated in favor of this variable.
120-
121119
Defines whether foreign key checking is done for applier threads.
122120
This is enabled by default.
123121

@@ -135,8 +133,6 @@ This is enabled by default.
135133
| Dynamic: | Yes |
136134
| Default Value: | ``1`` |
137135

138-
As of Percona XtraDB Cluster 8.0.26-16, the ``wsrep_slave_threads`` variable is deprecated and may be removed in a later version. Use the ``wsrep_applier_threads`` variable.
139-
140136
Specifies the number of threads
141137
that can apply replication transactions in parallel.
142138
Galera supports true parallel replication
@@ -173,8 +169,6 @@ For more configuration tips, see [`Setting Parallel Slave Threads` :octicons-lin
173169
| Dynamic: | Yes |
174170
| Default Value: | ``OFF`` |
175171

176-
As of *Percona XtraDB Cluster* 8.0.26-16, the ``wsrep_slave_UK_checks`` variable is deprecated and may be removed in a later version. Use the ``wsrep_applier_UK_checks`` variable.
177-
178172
Defines whether unique key checking is done for applier threads.
179173
This is disabled by default.
180174

@@ -212,31 +206,6 @@ It can be disabled in source-replica clusters.
212206

213207
[`MySQL wsrep option: wsrep_auto_increment_control` :octicons-link-external-16:](https://mariadb.com/docs/galera-cluster/reference/galera-cluster-system-variables#wsrep_auto_increment_control)
214208

215-
###`wsrep_causal_reads`
216-
217-
| Option | Descriptio n |
218-
| -------------- | ------------------ |
219-
| Command Line: | ``--wsrep-causal-reads`` |
220-
| Config File: | Yes |
221-
| Scope: | Global, Session |
222-
| Dynamic: | Yes |
223-
| Default Value: | ``OFF`` |
224-
225-
In some cases, the source may apply events faster than a replica,
226-
which can cause the source and replica to become out of sync for a brief moment.
227-
When this variable is set to `ON`, the replica will wait
228-
until that event is applied before doing any other queries.
229-
Enabling this variable will result in larger latencies.
230-
231-
!!! note
232-
233-
This variable was deprecated because enabling it is the equivalent of setting
234-
[`wsrep_sync_wait`](wsrep-system-index.md#wsrep_sync_wait) to `1`.
235-
236-
!!! admonition "See also"
237-
238-
[`MySQL wsrep option: wsrep_causal_reads` :octicons-link-external-16:](https://mariadb.com/docs/galera-cluster/reference/galera-cluster-system-variables#wsrep_causal_reads)
239-
240209
### `wsrep_certification_rules`
241210

242211
| Option | Description |
@@ -1043,8 +1012,6 @@ the whole DDL statement is not put under TOI.
10431012
| Dynamic: | Yes |
10441013
| Default Value: | ``OFF`` |
10451014

1046-
As of *Percona XtraDB Cluster* 8.0.26-16, the ``wsrep_restart_slave`` variable is deprecated in favor of this variable.
1047-
10481015
Defines whether the replication replica should be restarted
10491016
when the node joins the cluster.
10501017
Enabling this can be useful because the asynchronous replication replica thread
@@ -1053,25 +1020,7 @@ while the node is in a non-primary state.
10531020

10541021
!!! admonition "See also"
10551022

1056-
[MySQL wsrep option: wsrep_restart_slave :octicons-link-external-16:](https://mariadb.com/docs/galera-cluster/reference/galera-cluster-system-variables#wsrep_restart_replica)
1057-
1058-
### `wsrep_restart_slave`
1059-
1060-
| Option | Description |
1061-
| -------------- | ------------------ |
1062-
| Command Line: | ``--wsrep-restart-slave`` |
1063-
| Config File: | Yes |
1064-
| Scope: | Global |
1065-
| Dynamic: | Yes |
1066-
| Default Value: | ``OFF`` |
1067-
1068-
As of *Percona XtraDB Cluster* 8.0.26-16, the ``wsrep_restart_slave`` variable is deprecated and may be removed in later versions. Use ``wsrep_restart_replica``.
1069-
1070-
Defines whether the replication replica should be restarted
1071-
when the node joins the cluster.
1072-
Enabling this can be useful because the asynchronous replication replica thread
1073-
is stopped when the node tries to apply the next replication event
1074-
while the node is in a non-primary state.
1023+
[MySQL wsrep option: wsrep_restart_slave :octicons-link-external-16:](https://mariadb.com/docs/galera-cluster/reference/galera-cluster-system-variables?ask=#wsrep_restart_slave)
10751024

10761025
### `wsrep_retry_autocommit`
10771026

@@ -1129,74 +1078,6 @@ microseconds. Unit of variable is in microseconds, so set accordingly.
11291078
wait, and that can result in RSU starvation. User is expected to block
11301079
active RSU traffic while performing the operation.
11311080

1132-
### `wsrep_slave_FK_checks`
1133-
| Option | Description |
1134-
| -------------- | ------------------ |
1135-
| Command Line: | ``--wsrep-slave-FK-checks`` |
1136-
| Config File: | Yes |
1137-
| Scope: | Global |
1138-
| Dynamic: | Yes |
1139-
| Default Value: | ``ON`` |
1140-
1141-
As of *Percona XtraDB Cluster* 8.0.26-16, this variable is deprecated and may be removed in a later version. Use the ``wsrep_applier_FK_checks`` variable.
1142-
1143-
Defines whether foreign key checking is done for applier threads.
1144-
This is enabled by default.
1145-
1146-
### `wsrep_slave_threads`
1147-
1148-
| Option | Description |
1149-
| -------------- | ------------------ |
1150-
| Command Line: | ``--wsrep-slave-threads`` |
1151-
| Config File: | Yes |
1152-
| Scope: | Global |
1153-
| Dynamic: | Yes |
1154-
| Default Value: | ``1`` |
1155-
1156-
As of *Percona XtraDB Cluster* 8.0.26-16, this variable is deprecated and may be removed in a later version. Use the ``wsrep_applier_threads`` variable.
1157-
1158-
Specifies the number of threads
1159-
that can apply replication transactions in parallel.
1160-
Galera supports true parallel replication
1161-
that applies transactions in parallel only when it is safe to do so.
1162-
This variable is dynamic.
1163-
You can increase/decrease it at any time.
1164-
1165-
!!! note
1166-
1167-
When you decrease the number of threads,
1168-
it won’t kill the threads immediately,
1169-
but stop them after they are done applying the current transaction
1170-
(the effect with an increase is immediate, though).
1171-
1172-
If any replication consistency problems are encountered,
1173-
it’s recommended to set this back to `1` to see if that resolves the issue.
1174-
The default value can be increased for better throughput.
1175-
1176-
You may want to increase it as suggested
1177-
in [`Codership documentation for flow control` :octicons-link-external-16:](https://mariadb.com/docs/galera-cluster/galera-management/performance-tuning/flow-control-in-galera-cluster):
1178-
when the node is in ``JOINED`` state,
1179-
increasing the number of replica threads can speed up the catch-up to ``SYNCED``.
1180-
1181-
You can also estimate the optimal value for this from [`wsrep_cert_deps_distance`](wsrep-status-index.md#wsrep_cert_deps_distance) as suggested [in the MariaDB Galera Cluster documentation :octicons-link-external-16:](https://mariadb.com/docs/maxscale/reference/maxscale-monitors/galera-monitor).
1182-
1183-
For more configuration tips, see [this document :octicons-link-external-16:](https://mariadb.com/docs/galera-cluster/readme/about-galera-replication#galera-slave-threads).
1184-
1185-
### `wsrep_slave_UK_checks`
1186-
1187-
| Option | Description |
1188-
| -------------- | ------------------ |
1189-
| Command Line: | ``--wsrep-slave-UK-checks`` |
1190-
| Config File: | Yes |
1191-
| Scope: | Global |
1192-
| Dynamic: | Yes |
1193-
| Default Value: | ``OFF`` |
1194-
1195-
As of *Percona XtraDB Cluster* 8.0.26-16, this variable is deprecated and may be removed in a later version. Use the ``wsrep_applier_UK_checks`` variable.
1196-
1197-
Defines whether unique key checking is done for applier threads.
1198-
This is disabled by default.
1199-
12001081
### `wsrep_SR_store`
12011082

12021083
| Option | Description |
@@ -1219,8 +1100,6 @@ Defines storage for streaming replication fragments. The available values are `t
12191100
| Dynamic: | No |
12201101
| Default Value: | ``xtrabackup-v2, clone`` |
12211102

1222-
Percona XtraDB Cluster 8.4.4-1 adds `clone` to the default value. For older versions of Percona XtraDB Cluster, the default value is `xtrabackup-v2`.
1223-
12241103
This variable limits SST methods accepted by the server for [wsrep_sst_method](#wsrep_sst_method) variable. The default value is `xtrabackup-v2` or `clone`.
12251104

12261105
### `wsrep_sst_donor`
@@ -1291,9 +1170,9 @@ Available values are:
12911170

12921171
* `xtrabackup-v2`: Uses Percona XtraBackup to perform SST. This value is the default.
12931172
Privileges and permissions for running Percona XtraBackup
1294-
can be found in [Percona XtraBackup documentation :octicons-link-external-16:](https://docs.percona.com/percona-xtrabackup/8.4/privileges.html). For more information, see [Percona XtraBackup SST Configuration](xtrabackup-sst.md#percona-xtrabackup-sst-configuration). The `xtrabackup-v2` method supports clusters with GTIDs and async replicas.
1173+
can be found in [Percona XtraBackup documentation :octicons-link-external-16:](https://docs.percona.com/percona-xtrabackup/{{vers}}/privileges.html). For more information, see [Percona XtraBackup SST Configuration](xtrabackup-sst.md#percona-xtrabackup-sst-configuration). The `xtrabackup-v2` method supports clusters with GTIDs and async replicas.
12951174

1296-
* `clone`: Introduced in Percona XtraDB Cluster 8.4.4-4, uses the [clone method for SST](clone-sst.md).
1175+
* `clone`: Uses the [clone method for SST](clone-sst.md).
12971176

12981177
* `ist_only`: This value allows only Incremental State Transfer (IST). If a node cannot sync with the cluster with IST, abort that node's start. This action leaves the data directory unchanged. This value prevents starting a node that does not have a `grastate.dat` file after a manual backup restoration. This missing file could initiate a full-state transfer (SST), which can be more time- and resource-intensive.
12991178

0 commit comments

Comments
 (0)