Skip to content

Use master / another slave node when current node is failing #1056

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

Merged
merged 2 commits into from
Jun 19, 2019

Conversation

vmihailenco
Copy link
Collaborator

Replaces #1001
Fixes #945

@vmihailenco vmihailenco force-pushed the fix/do-not-use-random-node branch from a981ead to 1cc1ba9 Compare June 16, 2019 11:10
@thehydroimpulse
Copy link

this is great!

@vmihailenco vmihailenco merged commit fa2f6ee into master Jun 19, 2019
@vmihailenco vmihailenco deleted the fix/do-not-use-random-node branch June 19, 2019 08:02
vmihailenco added a commit that referenced this pull request Mar 11, 2020
Use master / another slave node when current node is failing
@tglunt
Copy link

tglunt commented Oct 17, 2020

Was there any reason to allow randomly choosing a failing node? Also wondering when using pipelining, why we don't mark a node as failing when receiving network errors

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

Successfully merging this pull request may close these issues.

Stop sending requests to the node down in cluster
3 participants