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

upgrade to zookeeper 3.4.6 #2

Open
wants to merge 1 commit into
base: 1.0
Choose a base branch
from
Open

upgrade to zookeeper 3.4.6 #2

wants to merge 1 commit into from

Conversation

grmblfrz
Copy link

@grmblfrz grmblfrz commented Jun 3, 2014

Not sure it that's all that is needed, but all tests are green...

@pkusnail
Copy link

pkusnail commented Jul 14, 2016

This project is quit out of date , elasticsearch 2.3 has been released already , and I encountered elasticsearch brain-split several times , I think zookeeper plugin maybe useful for elasticsearch brain-split problem, can elasticsearch brain-split problem be solved after installing zookeeper plugin in elasticsearch ,could you please answer my question ?

@imotov
Copy link
Owner

imotov commented Jul 15, 2016

@pkusnail the zookeeper plugin was created when the existing zen discovery was very flakey and prone to split-brains. This project was already unnecessary in v1.x time-frame, but I updated it to v1.0 enable users to upgrade before switching to zen discovery. Since then a lot of effort went into improving resiliency of elasticsearch. In the current state a properly configured elasticsearch v2.x cluster is much less likely to encounter resiliency problems than v0.90 or v1.0.0 with this plugin. Updating this plugin to v2.3 would require a lot of time that I don't currently have, and considering the current state of zen discovery I don't think creating another discovery plugin would be worth the effort.

If you are experiencing split-brains with 2.x branch, it is most likely caused by improper configuration. If this is the case, please, reconfigure your cluster using 3 dedicated master node setup described in the link above and if you are still experiencing issues, don't hesitate to reach out on Elasticsearch support forum with the description of the problem.

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.

3 participants