We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
环境: Linux,.net6.0, FreeRedis1.0.3,redis一主二从三哨兵
代码中使用方式: 哨兵方式连接,全局单例RedisClient。
复现过程: 停掉redis主节点,哨兵已选举出新的主节点,但是freeredis一直尝试连接之前的主节点,报错信息如下: System.Exception: 【172.24.43.38:10031/0】状态不可用,等待后台检查程序恢复方可使用。Connection refused 【172.24.43.38:10031/0】Next recovery time:03/13/2024 09:42:48 【172.24.43.38:10031/0】Next recovery time: 03/13/2024 09:42:54 (Connection refused) ...
The text was updated successfully, but these errors were encountered:
172.24.43.38:10031
是否能联通
Sorry, something went wrong.
172.24.43.38:10031 是否能联通
之前是可以联通的,我停掉以后就不能联通了。
172.24.43.38:10031是之前的master节点,我通过RedisClient的哨兵方式连接的。
但是我停掉master节点以后,哨兵已经选举出来了新的master节点,但是freeredis这边一直在尝试连接之前的master节点,也就是我停掉的172.24.43.38:10031。
说明哨兵还没有切换过来
No branches or pull requests
环境:
Linux,.net6.0, FreeRedis1.0.3,redis一主二从三哨兵
代码中使用方式:
哨兵方式连接,全局单例RedisClient。
复现过程:
停掉redis主节点,哨兵已选举出新的主节点,但是freeredis一直尝试连接之前的主节点,报错信息如下:
System.Exception: 【172.24.43.38:10031/0】状态不可用,等待后台检查程序恢复方可使用。Connection refused
【172.24.43.38:10031/0】Next recovery time:03/13/2024 09:42:48
【172.24.43.38:10031/0】Next recovery time: 03/13/2024 09:42:54 (Connection refused)
...
The text was updated successfully, but these errors were encountered: