Skip to content
New issue

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

AsyncRedisCluster: update slot mapping when the connection is down #262

Closed
sewenew opened this issue Aug 15, 2021 · 3 comments
Closed

AsyncRedisCluster: update slot mapping when the connection is down #262

sewenew opened this issue Aug 15, 2021 · 3 comments

Comments

@sewenew
Copy link
Owner

sewenew commented Aug 15, 2021

When connection is down, we also need to update the slot mapping. Because the corresponding master might been replace with a new one.

@zhangjie0125
Copy link

@sewenew

I meet a similiar issue.
My redis cluster servers need to be upgraded OS (CentOS7 -> Redhat8)

redis cluster server upgrade OS steps:

  1. stop one master node redis processes (in this step, role change should happen, there is a new redis master node at once)
  2. upgrade that master node OS
  3. run redis services and change it back to master node

But my client always get "Connection refused" exception, seems redis-plus-plus always try to reconnect to old master node

Environment:

  • OS: CentOS7
  • Compiler: g++4.8
  • hiredis version: v1.2.0
  • redis-plus-plus version: 1.3.11

So when will you add this feature?

@sewenew
Copy link
Owner Author

sewenew commented Sep 21, 2024

@zhangjie0125 With #595 fix, redis-plus-plus updates the slot-node mapping every ClusterOptions::slot_map_refresh_interval (by default, it updates every 10 seconds). Your problem should be solved with the latest code on master branch.

Regards

@sewenew
Copy link
Owner Author

sewenew commented Oct 1, 2024

Since there's no update, I'll close this issue. If you still have problem with it, feel free to reopen it.

Regards

@sewenew sewenew closed this as completed Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants