5 Commits

Author	SHA1	Message	Date
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
antirez	f62dfa0f50	Sentinel test: tolerate larger delays in init tests.	2014-06-19 15:58:45 +02:00
antirez	d06d8d6ffa	Sentinel test: unit 02, avoid some time related false positives.	2014-06-19 15:56:28 +02:00
antirez	f16ad11c71	Sentinel test: add manual failover test.	2014-06-19 10:33:12 +02:00
antirez	897adc1c8c	Sentinel test files / directories layout improved. ... The test now runs in a self-contained directory. The general abstractions to run the tests in an environment where mutliple instances are executed at the same time was extrapolated into instances.tcl, that will be reused to test Redis Cluster.	2014-04-24 11:08:22 +02:00