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

reconnect feature request #4

Open
virtser opened this issue Feb 23, 2014 · 5 comments
Open

reconnect feature request #4

virtser opened this issue Feb 23, 2014 · 5 comments

Comments

@virtser
Copy link
Contributor

virtser commented Feb 23, 2014

In case that I set a watch on some key.
What if etcd server is down or connection to server was lost?
How does the code reconnect?
In that case my application won't be notified of key value change.

@drusellers
Copy link
Owner

Agreed. I am going to define 'reconnect' for this issues as reconnecting to the same initially provided server. Etcetera needs to expose a timeout handler so that a user can 'rewatch' or take some other action as necessary.

@drusellers
Copy link
Owner

If my understanding of the TPL is correct - we can return a task on watch commands and then you could set handlers for the timeout / error / success - etc

@shamil
Copy link

shamil commented Jun 2, 2014

Is this still planned?
Also if I work with multi-machine etcd cluster, how can I specify all of them when creating client?

@drusellers
Copy link
Owner

A) Yes
B) Currently, you can't - we have been thinking about how to best approach this as well. This is planned though.

@smalldave
Copy link
Contributor

If it's of any use I started on this here
https://github.com/smalldave/etcetera/tree/noderetry
Stalled on the tests and unfortunately deadlines that pay the bills have stopped me going any further with it for a bit.

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

4 participants