diff options
author | Binbin <binloveplay1314@qq.com> | 2022-01-23 19:54:50 +0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-01-23 13:54:50 +0200 |
commit | 7e5ded2ad0521600ceb57d71b0dbb19bbbc087b7 (patch) | |
tree | d471a86ed1f8734e64701f972fa6e750061af3a8 /tests/cluster | |
parent | 23325c135f08365d1b7d4bf4fb1c9187fc7374b9 (diff) | |
download | redis-7e5ded2ad0521600ceb57d71b0dbb19bbbc087b7.tar.gz |
Fix timing issue in sentinel CKQUORUM test (#10036)
A test failure was reported in Daily CI (test-centos7-tls).
`CKQUORUM detects failover authorization cannot be reached`.
```
CKQUORUM detects failover authorization cannot be reached: FAILED:
Expected 'invalid command name "OK 4 usable Sentinels. Quorum and failover authorization can be reached"' to match '*NOQUORUM*'
```
It seems that current sentinel does not confirm that the other
sentinels are actually `down`, and then check the quorum.
It at least take 3 seconds on my machine, and we can see there
will be a timing issue with the hard code `after 5000`.
In this commit, we check the response of `SENTINEL SENTINELS mymaster`
to ensure that other sentinels are actually `down` in the view the
current sentinel. Solve the timing issue due to sentinel monitor mechanism.
Diffstat (limited to 'tests/cluster')
0 files changed, 0 insertions, 0 deletions