Valkey : Configure Sentinel2024/12/05

Configure Valkey Sentinel to provide high availability for Valkey Servers.

This example is based on the environment like follows.
If Primary Node would be down, Master role will failover to other Replica Node.

                                  |
+----------------------+          |          +----------------------+
|  [ valkey Sentinel ] |10.0.0.25 | 10.0.0.30|  [ valkey Primary ]  |
|    ctrl.srv.world    +----------+----------+    dlp.srv.world     |
|                      |          |          |                      |
+----------------------+          |          +----------------------+
                                  |
+----------------------+          |          +----------------------+
| [ valkey Replica#1 ] |10.0.0.51 | 10.0.0.52| [ valkey 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 valkey-sentinel

root@ctrl:~#

vi /etc/valkey/sentinel.conf

# line 15 : change (start service)

daemonize

yes

# line 92 : 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 112 : authentication password for Primary Node

sentinel auth-pass mymaster password

# line 125 : the duration Sentinel server looks Primary is down (30 sec by default)
# to change the parameter, uncomment the line and set your value

# sentinel down-after-milliseconds <master-name> <milliseconds>

# line 203 : add to set number of Replicas to be changed when running failover

sentinel parallel-syncs mymaster 1

root@ctrl:~#

systemctl restart valkey-sentinel

[3]	That's OK, verify status on Sentinel server like follows. Furthermore, stop valkey manually on Primary Node and make sure Primary/Replica failover normally.

root@ctrl:~#

valkey-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) "be361a637ddad897a8c7d4d42a7d3f8f55357310"
 9) "flags"
10) "master"
.....
.....

# show Replica Nodes for [mymaster]
127.0.0.1:26379> sentinel replicas mymaster 
1)  1) "name"
    2) "10.0.0.51:6379"
    3) "ip"
    4) "10.0.0.51"
    5) "port"
    6) "6379"
    7) "runid"
    8) "02d90be9eecd74dbc22904f50daf2960f4a8a369"
    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) "f1ff64d02d46e2c31a557dec150486c3419b747a"
    9) "flags"
   10) "slave"
.....
.....

Matched Content