You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I execute 'docker stop redis', the Docker will remove the host name mapping, but this situation can be understood as the node being unhealthy and causing a failover
Expected behavior
failover should start within configure time and slave nodes should be able to serve the request.
Additional information
1)when node went down failover is not happening and always getting resolve hostname error.
The text was updated successfully, but these errors were encountered:
Describe the bug
Sentinel failover does not happen when node went down.
Log display
when I execute
To reproduce
env detail:
deploy redis with sentinel in High Availiability mode(cluster size =3)
docker image redis:6.2.8
docker network create -d bridge mybridge
redis1.conf
redis2.conf
redis3.conf
sentinel1.conf
sentinel2.conf
sentinel3.conf
When I execute 'docker stop redis', the Docker will remove the host name mapping, but this situation can be understood as the node being unhealthy and causing a failover
Expected behavior
failover should start within configure time and slave nodes should be able to serve the request.
Additional information
1)when node went down failover is not happening and always getting resolve hostname error.
The text was updated successfully, but these errors were encountered: