Skip to content

Improve cluster resiliency to disconnected sub clusters + fix a shard allocation bug with quick rolling restarts #2042

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

Closed
kimchy opened this issue Jun 22, 2012 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Jun 22, 2012

Two main changes:

  1. Improve cluster resiliency to disconnected sub clusters. If a node pings a master and that node is no longer registered with the master, improve the rejoin process of that node to the cluster. Also, if a master receives a message from another master, pick one to force to rejoin the cluster (based on cluster state versioning).
  2. On quick rolling restart, without waiting for shard allocation, the shard allocation logic can mess up its counts, causing for strange logic in allocating shards, or validation failures on routing table allocation.
@kimchy
Copy link
Member Author

kimchy commented Jun 22, 2012

Fixed by #cc3fab45ffcc6d8208a35bcdc1bb9d8f7f7da7d8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant