1
MariaDB Replication
The terms master and slave have historically been used in replication, but the terms terms primary and replica are now preferred. The old terms are used still used in parts of the documentation, and in MariaDB commands, although MariaDB 10.5 has begun the process of renaming. The documentation process is ongoing. See MDEV-18777 to follow progress on this effort.
Replication is a feature allowing the contents of one or more primary servers to be mirrored on one or more replica servers.
-
Replication Overview
Allow the contents of one or more primary servers to be mirrored on one or more replicas. -
Replication Commands
List of replication-related commands. -
Setting Up Replication
Getting replication working involves steps on both the primary server/s and the replica server/s. -
Setting up a Replica with Mariabackup
Setting up a replica with Mariabackup. -
Read-Only Replicas
Making replicas 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 primary in parallel on the replica. -
Replication and Binary Log System Variables
Replication and binary log system variables. -
Replication and Binary Log Status Variables
Replication and binary log 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 replica from the primary 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 replicas to intentionally skip certain events. -
Running Triggers on the Replica for Row-based Events
Running triggers on the replica for row-based events. -
Semisynchronous Replication
Semisynchronous replication. -
Using MariaDB Replication with MariaDB Galera Cluster
Information on using MariaDB replication with MariaDB Galera Cluster. -
Delayed Replication
Specify that a replica should lag behind the primary by (at least) a specified amount of time. -
Replication When the Primary and Replica Have Different Table Definitions
Slave and the primary table definitions can differ while replicating. -
Restricting Speed of Reading Binlog from Primary by a Replica
The read_binlog_speed_limit option can be used to reduce load on the primary. -
Changing a Replica to Become the Primary
How to change a replica to primary and old primary as a replica for the new primary. -
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
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
