redict/tests/sentinel/tests
antirez e21e0ba3dc Sentinel test: more correct sentinels config reset.
In the initialization test for each instance we used to unregister the
old master and register it again to clear the config.
However there is a race condition doing this: as soon as we unregister
and re-register "mymaster", another Sentinel can update the new
configuration with the old state because of gossip "hello" messages.

So the correct procedure is instead, unregister "mymaster" from all the
sentinel instances, and re-register it everywhere again.
2014-06-23 14:07:47 +02:00
..
includes Sentinel test: more correct sentinels config reset. 2014-06-23 14:07:47 +02:00
00-base.tcl Sentinel test files / directories layout improved. 2014-04-24 11:08:22 +02:00
01-conf-update.tcl Sentinel test files / directories layout improved. 2014-04-24 11:08:22 +02:00
02-slaves-reconf.tcl Sentinel test: unit 02, avoid some time related false positives. 2014-06-19 15:56:28 +02:00
03-runtime-reconf.tcl Sentinel test files / directories layout improved. 2014-04-24 11:08:22 +02:00
04-slave-selection.tcl Sentinel test files / directories layout improved. 2014-04-24 11:08:22 +02:00
05-manual.tcl Sentinel test: add manual failover test. 2014-06-19 10:33:12 +02:00