Skip to content

Instantly share code, notes, and snippets.

@antirez
Created February 24, 2014 16:24
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save antirez/9191513 to your computer and use it in GitHub Desktop.
Save antirez/9191513 to your computer and use it in GitHub Desktop.
Starting sentinel #0 at port 20000
Starting sentinel #1 at port 20001
Starting sentinel #2 at port 20002
Starting sentinel #3 at port 20003
Starting sentinel #4 at port 20004
Starting redis #0 at port 30000
Starting redis #1 at port 30001
Starting redis #2 at port 30002
Starting redis #3 at port 30003
Starting redis #4 at port 30004
Testing unit: 00-base.tcl
> (init) Create a master-slaves cluster of 5 instances: OK
> (init) Sentinels can start monitoring a master: OK
> (init) Sentinels can talk with the master: OK
> (init) Sentinels are able to auto-discover other sentinels: OK
> (init) Sentinels are able to auto-discover slaves: OK
> Basic failover works if the master is down: OK
> New master 127.0.0.1:30003 role matches: OK
> All the other slaves now point to the new master: OK
> The old master eventually gets reconfigured as a slave: OK
> ODOWN is not possible without enough Sentinels reports: OK
> Failover is not possible without majority agreement: OK
> Failover works if we configure for absolute agreement: OK
> New master 127.0.0.1:30001 role matches: OK
Testing unit: 01-conf-update.tcl
> (init) Create a master-slaves cluster of 5 instances: OK
> (init) Sentinels can start monitoring a master: OK
> (init) Sentinels can talk with the master: OK
> (init) Sentinels are able to auto-discover other sentinels: OK
> (init) Sentinels are able to auto-discover slaves: OK
> We can failover with Sentinel 1 crashed: OK
> After Sentinel 1 is restarted, its config gets updated: OK
Testing unit: 02-slaves-reconf.tcl
Testing unit: 03-runtime-reconf.tcl
Cleaning up...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment