Introduction to the principle of Redis master-slave replication (picture and text)

This article brings you an introduction to the principles of Redis master-slave replication (pictures and texts). It has certain reference value. Friends in need can refer to it. I hope it will be helpful to you.

Facing problems

1. Machine failure. We deploy to a Redis server. When a machine failure occurs, we need to migrate to another server and ensure that the data is synchronized. Data is the most important thing. If you don't care, you basically won't use Redis.

2. Capacity bottleneck. When we need to expand the Redis memory, from 16G memory to 64G, a single machine will definitely not be able to satisfy it. Of course, you can buy a new 128G machine.

Solution

To achieve greater storage capacity of the distributed database and withstand high concurrent access, we will store the data of the original centralized database separately. on multiple other network nodes.

In order to solve the problem of this single node, Redis will also replicate multiple copies of the data and deploy them to other nodes for replication to achieve high availability of Redis and redundant backup of data to ensure data and services. High availability.

Master-slave replication

What is master-slave replication

Master-slave replication refers to copying the data of a Redis server to other Redis servers. The former is called the master node, and the latter is called the slave node. Data replication is one-way, and can only be from the master node to the slave node.

By default, each Redis server is a master node; and a master node can have multiple slave nodes (or no slave nodes), but a slave node can only have one master node.

The role of master-slave replication

1. Data redundancy: Master-slave replication implements hot backup of data, which is a data redundancy method other than persistence.

2. Failure recovery: When a problem occurs on the master node, the slave node can provide services to achieve rapid failure recovery; it is actually a kind of service redundancy.

3. Load balancing: Based on master-slave replication, combined with read-write separation, the master node can provide write services and the slave nodes can provide read services (that is, when writing Redis data, apply the connection Master node, when reading Redis data, connect to the slave node) to share the server load; especially in scenarios where there is less writing and more reading, sharing the read load through multiple slave nodes can greatly increase the concurrency of the Redis server.

4. Read and write separation: It can be used to achieve read and write separation, main library writing, slave library reading. Reading and writing separation can not only improve the load capacity of the server, but also can be used according to changes in demand. Change the number of slave libraries;

5. Cornerstone of high availability: In addition to the above functions, master-slave replication is also the basis for the implementation of sentinels and clusters. Therefore, master-slave replication is the basis of Redis high availability. .

Enable master-slave replication

Enable master-slave replication from the slave node. There are 3 ways:

1. Configuration file: In Add from the server's configuration file: slaveof

2. Start command: Add --slaveof after redis-server starts the command.

3. Client command: After the Redis server is started, execute the command directly through the client: slaveof
   , then the Redis instance becomes a slave node.

You can see some replication information through the info replication command

Master-slave replication principle

The master-slave replication process can be roughly divided into three stages : Connection establishment phase (i.e. preparation phase), data synchronization phase, command propagation phase.

After the slave node executes the slaveof command, the replication process starts to operate. You can roughly see the picture below.
It can be seen from the picture that the replication process is roughly divided into 6 processes

The log records after the master-slave configuration can also see this process

1) Save the master node (master) information.
After executing slaveof, Redis will print the following log:

2) The slave node (slave) maintains replication-related logic through scheduled tasks that run every second. When the scheduled task After discovering the existence of a new master node, it will try to establish a network connection with the node

The slave node will establish a network connection with the master node

The slave node will establish a socket socket, the slave node establishes a socket with port 51234, which is specially used to accept replication commands sent by the master node. After the slave node is successfully connected, the following log is printed:

If the slave node cannot establish a connection, the scheduled task will retry indefinitely until the connection is successful or execute slaveof no one to cancel replication

Regarding connection failure, you can execute it on the slave node info replication View the master_link_down_since_seconds metric, which records the system time when the connection to the master node failed. When the slave node fails to connect to the master node, the following log will be printed every second to facilitate problem discovery:

# Error condition on socket for SYNC: {socket_error_reason}

3) Send the ping command.
After the connection is successfully established, the slave node sends a ping request for the first communication. The main purpose of the ping request is as follows:
·Detect whether the network socket between the master and slave is available.
·Detect whether the master node can currently accept processing commands.
If after sending the ping command, the slave node does not receive the pong reply from the master node or times out, such as the network times out or the master node is blocked and cannot respond to the command, the slave node will disconnect the replication connection, and the next scheduled task will initiate a reconnection. .

The ping command sent from the node returns successfully, Redis prints the following log, and continues the subsequent replication process:

4) Permission verification. If the requirepass parameter is set on the master node, password verification is required. The slave node must configure the masterauth parameter to ensure that the password is the same as the master node to pass the verification; if the verification fails, the replication will be terminated and the slave node will reinitiate the replication process.

5) Synchronize data sets. After the master-slave replication connection communicates normally, when replication is established for the first time, the master node will send all the data it holds to the slave node. This part of the operation is the longest step.

6) The command is copied continuously. When the master node synchronizes the current data to the slave node, the replication establishment process is completed. Next, the master node will continuously send write commands to the slave nodes to ensure master-slave data consistency.

The above is the detailed content of Introduction to the principle of Redis master-slave replication (picture and text). For more information, please follow other related articles on the PHP Chinese website!