Debian 11 Bullseye
Sponsored Link

Redis 6 : Configure Redis Sentinel
2021/09/21
 
Configure Redis Sentinel to provide high availability for Redis Servers.
This example is based on the environment like follows.
If Primary Node would be down, Master role will failover to other Replica Node.
                                  |
+----------------------+          |          +----------------------+
|  [ Redis Sentinel ]  |10.0.0.25 | 10.0.0.30|   [ Redis Primary ]  |
|    ctrl.srv.world    +----------+----------+    dlp.srv.world     |
|                      |          |          |                      |
+----------------------+          |          +----------------------+
                                  |
+----------------------+          |          +----------------------+
| [ Redis Replica#1 ]  |10.0.0.51 | 10.0.0.52|  [ Redis Replica#2 ] |
|   node01.srv.world   +----------+----------+    node02.srv.world  |
|                      |                     |                      |
+----------------------+                     +----------------------+

[1]
Configure replication Settings on all Primary and Replica Nodes, refer to here.
Points to be aware of regarding replication settings, it needs to set the same authentication password on all Nodes.
[2] Configure Sentinel Server.
root@ctrl:~#
apt -y install redis-sentinel
root@ctrl:~#
vi /etc/redis/sentinel.conf
# line 16 : change

bind
0.0.0.0
::1
# line 27 : confirm setting (start service)

daemonize yes
# line 85 : change
# [sentinel monitor (any name) (Primary's IP) (Primary's Port) (Quorum)]
# Quorum ⇒ run failover when the specified number of Sentinel servers look Primary is down

sentinel monitor mymaster 10.0.0.30 6379 1
# line 105 : authentication password for Primary Node

sentinel auth-pass mymaster password
# line 126 : the duration Sentinel server looks Primary is down (30 sec by default below)

sentinel down-after-milliseconds mymaster 30000
# line 142 : number of Replicas to be changed when running failover

sentinel parallel-syncs mymaster 1
root@ctrl:~#
systemctl restart redis-sentinel

[3] That's OK, verify status on Sentinel server like follows.
Furthermore, stop Redis manually on Primary Node and make sure Primary/Replica failover normally.
root@ctrl:~#
redis-cli -p 26379

# show Primary Node for [mymaster]
127.0.0.1:26379> sentinel get-master-addr-by-name mymaster 
1) "10.0.0.30"
2) "6379"

# show details of Primary Node for [mymaster]
127.0.0.1:26379> sentinel master mymaster 
 1) "name"
 2) "mymaster"
 3) "ip"
 4) "10.0.0.30"
 5) "port"
 6) "6379"
 7) "runid"
 8) "24e63ae9cc7e051ab6dd7d45e0d4c8643848d7aa"
 9) "flags"
10) "master"
.....
.....

# show Replica Nodes for [mymaster]
127.0.0.1:26379> sentinel slaves mymaster 
1)  1) "name"
    2) "10.0.0.51:6379"
    3) "ip"
    4) "10.0.0.51"
    5) "port"
    6) "6379"
    7) "runid"
    8) "e4abcf2133265a530a1d003cbd2c615f14aaec16"
    9) "flags"
   10) "slave"
   .....
   .....

2)  1) "name"
    2) "10.0.0.52:6379"
    3) "ip"
    4) "10.0.0.52"
    5) "port"
    6) "6379"
    7) "runid"
    8) "db1dbbae22ecbfa38863e6e0f73a08b0b14a68a2"
    9) "flags"
   10) "slave"
   .....
   .....
Matched Content