February 2018
Intermediate to advanced
382 pages
11h 33m
English
In this experiment, we manually forced the Sentinel to failover the Redis master and promote a slave. This was done by issuing the command sentinel failover <master-name> to Sentinel-2. As we can see, 192.168.0.33 was promoted to the new master and the old master became a slave.
Now, let's take a look at the process in detail from the log of Sentinel-2; there are multiple Sentinel events (+vote-for-leader, +elected-leader, +selected-slave, and so on). Most of them are self-explanatory by name, but you can find a table of all Sentinel events in the There's more section.
Read now
Unlock full access