Replication is a feature allowing the contents of one or more master servers to be mirrored on one or more slave servers.
Title | Description |
---|---|
Replication Overview | Allow the contents of one or more master servers to be mirrored on one or more slave servers. |
Replication Commands | List of replication-related commands |
Setting Up Replication | Getting replication working involves steps on both the master server/s and the slave server/s. |
Setting up a Replication Slave with Mariabackup | Setting up a replication slave with Mariabackup. |
Read only slaves | Making slaves read only |
Replication as a Backup Solution | Replication can be used to support the backup strategy. |
Multi-Source Replication | Using replication with many masters. |
Replication Threads | Types of threads that are used to enable replication. |
Global Transaction ID | Improved replication using global transaction IDs. |
Parallel Replication | Executing queries replicated from the master in parallel on the slave. |
Replication and Binary Log System Variables | Replication and binary log system variables. |
Replication and Binary Log Status Variables | Replication and Binary Log Server Status Variables |
Binary Log | Contains a record of all changes to the databases, both data and structure |
Unsafe Statements for Statement-based Replication | Statements that are not safe for statement-based replication. |
Replication and Foreign Keys | Cascading deletes or updates based on foreign key relations are not written to the binary log |
Relay Log | Event log created by the slave from the master binary log |
Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT | Enhancements for START TRANSACTION WITH CONSISTENT SNAPSHOT. |
Group Commit for the Binary Log | Optimization when the server is run with innodb_flush_logs_at_trx_commit or sync_binlog. |
Selectively Skipping Replication of Binlog Events | @@skip_replication and --replicate-events-marked-for-skip |
Binlog Event Checksums | Including a checksum in binlog events |
Binlog Event Checksum Interoperability | Replicating between servers with differing binlog checksum availability |
Annotate_rows_log_event | Annotate_rows events accompany row events and describe the query which caused the row event |
Row-based Replication With No Primary Key | MariaDB improves on row-based replication of tables with no primary key |
Replication Filters | Replication filters allow users to configure replication slaves to intentio... |
Running Triggers on the Slave for Row-based Events | Running triggers on the slave for Row-based events |
Semisynchronous Replication | Semisynchronous replication. |
Using MariaDB Replication with MariaDB Galera Cluster | Information on using MariaDB replication with MariaDB Galera Cluster. |
Compressing Events to Reduce Size of the Binary Log | Binlog events can be compressed to save space on disk and in network transfers |
Delayed Replication | Specify that a slave should lag behind the master by (at least) a specified amount of time |
Replication When the Master and Slave Have Different Table Definitions | Slave and the master table definitions can differ while replicating. |
Restricting speed of reading binlog from master by a slave | Restricting speed of reading binlog from master by a slave When a slave sta... |
Changing a Slave to Become the Master | How to change a slave to master and old master as a slave for the new master. |
Replication with Secure Connections | Enabling TLS encryption in transit for MariaDB replication. |
Obsolete Replication Information | This section is for replication-related items that are obsolete |
© 2019 MariaDB
Licensed under the Creative Commons Attribution 3.0 Unported License and the GNU Free Documentation License.
https://mariadb.com/kb/en/high-availability-performance-tuning-mariadb-replication/