This article original from the http://blog.csdn.net/voipmaker reprint indicate the source.
Redis HA aims to automatically upgrade from the master node to the master node after the master node fails.
The current solutions are as follows:
(1) redis-cluster built-in ha function, redis 3.0 implements the cluster function, built-in ha.
This function is only supported in cluster mode. After the master node fails, the slave will be automatically upgraded to the master node, which is hidden from the client.
(2) keepalived and virtual IP address Solution
The traditional HA solution uses keealived to monitor the redis Process status. After the master fails, slave synchronizes the master database (persistent) and takes over the master. You need to write a script to implement this process.
(3) Implementation through redis-Sentinel
The HA solution officially implemented by redis uses the redis-sentinel process to monitor the Master Status. When the master fails, the slave is automatically upgraded to the master. the redis client must support sentianel. When ha occurs, the client queries sentianel to obtain the access information of the current master node.
HA solution for redis practices