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

I'm using async api, but when cluster node timeout, it will synchronously connect cluster node when updating route #122

Open
lcygosky opened this issue Aug 13, 2019 · 1 comment

Comments

@lcygosky
Copy link

No description provided.

@thakurajayL
Copy link

Thats right and it gets blocked forever. Chances are there that your heart-bit monitoring task might kill the process if its stuck.
I had done code to solve this issue but did not commit and unfortunately I lost the code as well.

  1. When route table is required due to any error call the async callback in the application.
  2. This async callback should initiate raw command (0 second timer) to get "cluster nodes" from the Redis cluster.
    Now Cluster nodes command can be fired to any one of the nodes (cluster mode)
  3. When response is received Application can feed the response to redis lib and it can then update its routing table.

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