Master-slave synchronization for Redis and master-slave for redis

Master-slave synchronization for Redis and master-slave for redis

Synchronization

Why does Redis implement master-slave synchronization?

Master-slave synchronization has the following benefits:

Partial re-synchronization

Redis introduced PSYNC starting from 2.8 and supports partial re-synchronization: during this period of time when the master server and slave server are disconnected, the data on the master server may only change a small amount, when the slave server is re-connected to the master server, there is no need to send all the data in the master server to the slave server for data coverage. Instead, you only need to send inconsistent data to the slave server, this avoids data backup and network transmission on the master server.

Synchronization Process

The following two machines are used: A (10.15.62.11: 6379) as the slave server and B (10.15.62.12: 6380) as the master server, this section describes the initial full synchronization and partial re-synchronization of A and B.

Code implementation:

To be continued.

References:

Redis design and implementation chapter 15th

Redis master-Slave synchronization source code analysis-Slave end