mirrors/valkey
1
0
Fork 0
mirror of http://github.com/valkey-io/valkey synced 2024-11-23 03:33:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Sentinel test: test majority crashing Sentinels.

Browse Source 
The test was previously performed by removing the master from the
Sentinel monitored masters. The test with the Sentinels crashed is
more similar to real-world partitions / failures.
This commit is contained in:
antirez 2014-02-25 08:29:12 +01:00
parent 630fb3539f
commit 044b627549
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
tests/sentinel-tests/00-base.tcl
View File

@ -42,7 +42,7 @@ test "The old master eventually gets reconfigured as a slave" {
}
}
test "ODOWN is not possible without enough Sentinels reports" {
test "ODOWN is not possible without N (quorum) Sentinels reports" {
foreach_sentinel_id id {
S $id SENTINEL SET mymaster quorum [expr $sentinels+1]
}
@ -61,22 +61,20 @@ test "Failover is not possible without majority agreement" {
S $id SENTINEL SET mymaster quorum $quorum
}
# Make majority of sentinels stop monitoring the master
# Crash majority of sentinels
for {set id 0} {$id < $quorum} {incr id} {
S $id SENTINEL REMOVE mymaster
kill_instance sentinel $id
}
R $master_id debug sleep 10
# Make sure failover did not happened.
set addr [S $quorum SENTINEL GET-MASTER-ADDR-BY-NAME mymaster]
assert {[lindex $addr 1] == $old_port}
# Cleanup: reconfigure the Sentinels to monitor the master.
# Cleanup: restart Sentinels to monitor the master.
for {set id 0} {$id < $quorum} {incr id} {
S $id SENTINEL MONITOR mymaster \
[get_instance_attrib redis $master_id host] \
[get_instance_attrib redis $master_id port] $quorum
S $id SENTINEL SET mymaster down-after-milliseconds 2000
restart_instance sentinel $id
}
}