PXC-4771 [DOCS] - Update name and links for Galera cluster 8.0 (#303)

Author: alina-derkach-oaza

docs/crash-recovery.md

@@ -51,7 +51,7 @@ $ systemctl start mysql
 ```
 !!! admonition "See also"
 
-    [Galera Documentation: wsrep_sst_donor option](https://galeracluster.com/library/documentation/mysql-wsrep-options.html#wsrep-sst-donor)
+    [MariaDB Galera Documentation: wsrep_sst_donor option](https://mariadb.com/docs/galera-cluster/reference/galera-cluster-system-variables#wsrep_sst_donor)
 
 ## Scenario 3: All three nodes are gracefully stopped
 

docs/faq.md

@@ -120,7 +120,7 @@ in a new component strictly exceeds half that
 of the preceding Primary Component,
 minus the nodes which left gracefully.
 
-The mechanism is described in detail in [Galera documentation](https://galeracluster.com/library/documentation/index.html).
+The mechanism is described in detail in [MariaDB Galera Cluster](https://mariadb.com/docs/galera-cluster/).
 
 ## How would the quorum mechanism handle split brain?
 
@@ -138,7 +138,7 @@ wsrep_provider_options="pc.ignore_sb = yes"
 ## Why a node stops accepting commands if the other one fails in a 2-node setup?
 
 This is expected behavior to prevent [split brain](glossary.md#split-brain).
-For more information, see previous question or [Galera documentation](https://galeracluster.com/library/documentation/index.html).
+For more information, see previous question or [MariaDB Galera Cluster](https://mariadb.com/docs/galera-cluster/).
 
 ## Is it possible to set up a cluster without state transfer?
 

docs/garbd-howto.md

@@ -4,7 +4,7 @@ The size of a cluster increases when a node joins the cluster and decreases when
 
 The arbitrator is important if you have an even number of nodes remaining in the cluster. The arbitrator keeps the number of nodes as an odd number, which avoids the split-brain situation.
 
-A [Galera Arbitrator](https://galeracluster.com/library/documentation/arbitrator.html)
+A [Galera Arbitrator](https://mariadb.com/docs/galera-cluster/high-availability/understanding-quorum-monitoring-and-recovery#the-galera-arbitrator-garbd)
 is a lightweight member of a **Percona XtraDB Cluster**. This member can vote but does not do any replication and is not included in flow control calculations. The Galera Arbitrator is a separate daemon called `garbd`. You can start this daemon separately from the cluster and run this daemon either as a service or from the shell. You cannot configure this daemon using the `my.cnf` file.
 
 !!! note
@@ -36,7 +36,7 @@ root@ubuntu:~# apt install percona-xtradb-cluster-garbd
 
     It is necessary to specify the cipher. In this example, it is `AES128-SHA256`. If you do not specify the cipher, an error occurs with a “Terminate called after throwing an instance of ‘gnu::NotSet’” message.
 
-    For more information, see [socket.ssl_cipher](https://galeracluster.com/library/documentation/galera-parameters.html#socket-ssl-cipher)
+    For more information, see [socket.ssl_cipher](https://mariadb.com/docs/galera-cluster/reference/wsrep-variable-details/wsrep_provider_options#socket.ssl_cipher)
 
 When starting from the shell, you can set the parameters from the command line or edit the configuration file. This is an example of starting from the command line:
 

docs/limitation.md

@@ -72,7 +72,7 @@ The following limitations apply to Percona XtraDB Cluster:
 
     !!! admonition "See also"
 
-        [Galera Documentation: Tables without Primary Keys](https://galeracluster.com/library/training/tutorials/differences.html#tables-without-primary-keys)
+        [MariaDB Galera Documentation: Tables without Primary Keys](https://mariadb.com/docs/server/architecture/server-constraints/primary-key-constraints)
         
 * When configuring Percona XtraDB Cluster, your server must create a local socket.
 

docs/online-schema-upgrade.md

@@ -8,7 +8,7 @@ Percona XtraDB Cluster supports the following methods for making online schema c
 
 | Method Name| Reason for use| Description|
 | ----------- | -------------- | ------------- |
-| [TOI or Total Order Isolation]| Consistency is important. | Other transactions are blocked while the cluster processes the DDL statements. This is the default method for the [wsrep-OSU-method](https://galeracluster.com/library/documentation/mysql-wsrep-options.html#wsrep-osu-method) variable. The isolation of the DDL statement guarantees consistency. The DDL replication uses a statement format with each node processing the replicated DDL statement at the same position in the replication stream. All other writes must wait until the DDL statement is executed. Long-running transactions using the same resources may receive a deadlock error at commit and be rolled back. The [pt-online-schema-change](https://www.percona.com/doc/percona-toolkit/LATEST/pt-online-schema-change.html) in the Percona Toolkit can alter the table without using locks. There are limitations: only InnoDB tables can be altered, and the `wsrep_OSU_method` must be `TOI`.|
+| [TOI or Total Order Isolation]| Consistency is important. | Other transactions are blocked while the cluster processes the DDL statements. This is the default method for the [wsrep-OSU-method](https://mariadb.com/docs/galera-cluster/reference/galera-cluster-system-variables#wsrep_osu_method) variable. The isolation of the DDL statement guarantees consistency. The DDL replication uses a statement format with each node processing the replicated DDL statement at the same position in the replication stream. All other writes must wait until the DDL statement is executed. Long-running transactions using the same resources may receive a deadlock error at commit and be rolled back. The [pt-online-schema-change](https://www.percona.com/doc/percona-toolkit/LATEST/pt-online-schema-change.html) in the Percona Toolkit can alter the table without using locks. There are limitations: only InnoDB tables can be altered, and the `wsrep_OSU_method` must be `TOI`.|
 | [RSU or Rolling Schema Upgrade]| This method guarantees high availability during the schema upgrades.| The node desynchronizes with the cluster and disables flow control during the execution of the DDL statement. The rest of the cluster is not affected. After the statement execution, the node applies delayed events and synchronizes with the cluster. Although the cluster remains active, some nodes have the newer schema and some nodes have the older schema during the process. The RSU method is a manual operation, requiring the `gcache` to be large enough to store the data for the duration of the DDL change.|
 | [NBO or Non-Blocking Operation]| This method is used when consistency is important and uses a more efficient locking strategy.| This method is similar to `TOI`. DDL operations acquire an exclusive metadata lock on the table or schema at a late stage of the operation when updating the table or schema definition. Attempting a State Snapshot Transfer (SST) fails during the NBO operation. This mode uses a more efficient locking strategy and avoids the `TOI` issue of long-running DDL statements blocking other updates in the cluster. |
 

docs/state-snapshot-transfer.md

@@ -80,7 +80,7 @@ CREATE TABLE t1 (c1 INT PRIMARY KEY) DATA DIRECTORY = '/alternative/directory';
 ### SST using Percona XtraBackup
 
 XtraBackup will restore the table to the same location on the joiner node.  If
-the target directory does not exist, it will be created.  If the target file
+the target directory does not exist, it will be created. If the target file
 already exists, an error will be returned, because XtraBackup cannot clear
 tablespaces not in the data directory.
 
@@ -90,4 +90,4 @@ For more information, see:
 
 * [Xtrabackup SST configuration](xtrabackup-sst.md#percona-xtrabackup-sst-configuration)  
 
-* [State Snapshot Transfer Methods for MySQL](https://galeracluster.com/library/documentation/sst.html)  
+* [State Snapshot Transfer Methods for MySQL](https://mariadb.com/docs/galera-cluster/high-availability/state-snapshot-transfers-ssts-in-galera-cluster/introduction-to-state-snapshot-transfers-ssts/)  

docs/wsrep-provider-index.md

@@ -1,7 +1,6 @@
 # Index of wsrep_provider options
 
-The following variables can be set and checked in the [`wsrep_provider_options`](wsrep-system-index.md#wsrep_provider_options) variable. The value of the variable can be
-changed in the *MySQL* configuration file, `my.cnf`, or by setting the variable value in the *MySQL* client.
+The following variables can be set and checked in the [`wsrep_provider_options`](wsrep-system-index.md#wsrep_provider_options) variable. The value of the variable can be changed in the *MySQL* configuration file, `my.cnf`, or by setting the variable value in the *MySQL* client.
 
 To change the value in `my.cnf`, the following syntax should be used:
 
@@ -97,9 +96,9 @@ should be logged.
 
 !!! admonition "See also"
 
-    Galera Cluster Documentation:
-    * [Parameter: cert.optimistic_pa](https://galeracluster.com/library/documentation/galera-parameters.html#cert-optimistic-pa)
-    * [Setting parallel slave threads](https://galeracluster.com/library/kb/parallel-slave-threads.html)
+    MariaDB Galera Cluster Documentation:
+    * [Parameter: cert.optimistic_pa](https://mariadb.com/docs/galera-cluster/reference/galera-cluster-system-variables/#cert-optimistic-pa)
+    * [Setting parallel slave threads](https://mariadb.com/docs/galera-cluster/readme/about-galera-replication#galera-slave-threads)
 
 ### `debug`
 
@@ -515,9 +514,7 @@ size of the disk. Pages are prefixed by gcache.page.
 
 !!! admonition "See also"
 
-      * [Galera Documentation: gcache.page_size](https://galeracluster.com/library/documentation/galera-parameters.html#gcache-page-size)
-
-      * [Percona Database Performance Blog: All You Need to Know About GCache](https://www.percona.com/blog/2016/11/16/all-you-need-to-know-about-gcache-galera-cache/)
+    [Percona Database Performance Blog: All You Need to Know About GCache](https://www.percona.com/blog/2016/11/16/all-you-need-to-know-about-gcache-galera-cache/)
 
 ### `gcache.recover`
 
@@ -584,7 +581,7 @@ rr
 
 !!! admonition "See also"
 
-    For information, see the [Galera Cluster documentation](https://galeracluster.com/library/documentation/galera-parameters.html#gcomm-thread-prio)
+    For information, see the [MariaDB Galera Cluster documentation](https://mariadb.com/docs/galera-cluster/reference/wsrep-variable-details/wsrep_provider_options#gcomm.thread_prio)
 
 ### `gcs.fc_auto_evict_threshold`