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

Zookeeper, etcd support multiple IPs but datastore.newClient only takes one. #507

Closed
alfredr opened this issue Sep 9, 2015 · 2 comments
Closed
Milestone

Comments

@alfredr
Copy link

alfredr commented Sep 9, 2015

Zookeeper, etcd support multiple ips but datastore.newClient only takes one.

This can cause inability to restart docker if the Zookeeper or etcd peer specified in kvstore argument goes down -- even if the other n-1 are up.

Further it appears that this list is the complete list of alternate backends that go-zookeeper/etcd client libraries will try in the event of a failure, meaning that if only one is specified it constitutes a single point of failure.

@mavenugo
Copy link
Contributor

Thanks for reporting the issue. we will take a look at this

@mavenugo mavenugo added this to the 0.5 milestone Sep 10, 2015
@GordonTheTurtle
Copy link

@alfredr It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

  • For a bug: do you still experience the issue with the latest version?
  • For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to #1926

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

3 participants