Method and system for realizing redis automatic master-slave switching

Abstract

The invention provides a method and a device for achieving automatic Redis master-slave conversion. The device includes a Redis cache control center, a broadcasting service framework, subsystems and Redis nodes. The Redis cache control center is used for storing configuration information, providing registration service for the broadcasting service framework, monitoring the Redis nodes, changing master-slave configuration information in a memory when a Redis master server is not alive and sending master-slave conversion commands to the broadcasting service framework. The broadcasting service framework is used for obtaining the broadcasting conversion commands of each subsystem of Redis linkage information from the Redis cache control center after receiving the master-slave conversion commands from the Redis cache control center. The subsystems are used for conducting master-slave conversion after receiving broadcasting of the broadcasting service framework. The Redis nodes serve as a cache layer between the subsystems and a database.

Description

technical field [0001] The invention relates to a method and system for realizing Redis automatic master-slave switching. Background technique [0002] At present, in order to solve the performance problems caused by high concurrency, web application systems will adopt a cache layer between the web application system and the database. The most widely used is Redis (Redis is essentially a key-value type memory database). Due to its high performance and simple operation commands, Redis can be used as a buffer between software and traditional databases, ensuring high performance while ensuring data validity. [0003] At present, Redis only supports master-slave backup, but the released version does not support automatic master-slave switching after encountering problems. At present, there are mainly two solutions for this: [0004] The first solution uses Redis double writing, which is performed by writing two copies of the application server. In this solution, the consistenc...

AI Technical Summary

Problems solved by technology

In this solution, the Keepalived software needs to be installed separately, and the scripts and configuration files described in the configuration solution need to be configured, which increases the learning cost and is prone to errors; the localization strategy must be enabled on both the master and the slave, otherwise it will not be enabled during the automatic switching process. The localized party will clear the data of the other party, resulting in complete data loss; it cannot implant the business logic of its own system, and can only perform stateless monitoring and master-slave switching, for example, monitoring with specific business logic cannot be achieved And the record of the cause of the problem when the master-slave is switched; it is inconvenient to add a new Redis machine later, and the configuration file needs to be changed

Images