How does MariaDB implement master-slave replication and what replication modes are available? - 面试题

MariaDB provides multiple replication methods to meet different scenario requirements:

1. Master-Slave Replication

Asynchronous Replication:

Master returns immediately after executing transactions, without waiting for slave confirmation
Best performance, but may have data latency
Use cases: Read-heavy, low data consistency requirements

Semi-Synchronous Replication:

Master waits for at least one slave to confirm receiving the transaction before returning
Balances performance and data consistency
Use cases: Scenarios requiring higher data consistency

2. Group Replication

Multi-master replication based on Paxos algorithm
Supports automatic failover
Provides strong consistency guarantees
Use cases: Production environments requiring high availability and reliability

3. Galera Cluster

Synchronous multi-master replication
All nodes can read and write
No data loss risk
Use cases: Scenarios requiring high availability and read-write load balancing

4. GTID Replication

Uses Global Transaction IDs to identify transactions
Simplifies failover and master-slave switching
Easier to manage replication topology
Use cases: Complex replication environments

Configuration Example

sql
-- Master configuration
server-id = 1
log-bin = mysql-bin
binlog-format = ROW
gtid-mode = ON
enforce-gtid-consistency = ON

-- Slave configuration
server-id = 2
relay-log = relay-bin
read-only = 1

Monitoring Replication Status

sql
-- Check master status
SHOW MASTER STATUS;

-- Check slave status
SHOW SLAVE STATUS;

When choosing a replication method, consider: performance requirements, data consistency requirements, failover capability, operational complexity, and other factors.