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

No failover policy when coordinating through partitioned off nodes #667

Open
michaelsembwever opened this issue Sep 17, 2014 · 0 comments
Open

Comments

@michaelsembwever
Copy link
Contributor

Yesterday we had one node in our cluster completely partition off from the rest of the cluster.

Our applications written with hector suffered downtime
from "HUnavailableException: : May not be enough replicas present to handle consistency level."

Request consistency level was ONE. But connecting to the partitioned off node as the coordinator meant that replica were often on other unreachable nodes. This explains the error message above.

Looking into HConnectionManager.operateWithFailover(..) it's clear that any HUnavailableException is immediately thrown. This makes sense when the coordinator is part of the healthy cluster and the replica required are on down nodes since no future request to other healthy coordinators are going to get around the problem that those replica are down. But it doesn't make sense when the coordinator is a node partitioned away from the cluster, as a future request will go to a different coordinator, likely healthy, and find required replica.

I haven't supplied any patch / pr as i'm unsure as to how this should be handled…

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

1 participant