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

Question: how to watch for cluster events? #5357

Closed
celevra opened this issue May 14, 2016 · 3 comments
Closed

Question: how to watch for cluster events? #5357

celevra opened this issue May 14, 2016 · 3 comments

Comments

@celevra
Copy link

celevra commented May 14, 2016

Hi,

i'm on a 3 node CoreOS and i want to listn to cluster events, i think fleet does this allready, doesn't it?

I need to know as fast as possible if one node is down, so that i can switch my ClusterIP's
etcd knows allready when a node is available or not so how can i listn to that events?
I don't want to call /health every few seconds, i think there must be a elegant way.

regards

celevra

@xiang90
Copy link
Contributor

xiang90 commented May 17, 2016

There is no magic way to do that actually. Internally, etcd also does simple health checking between every pairs of nodes. Externally, you have to ping each node to know its status against your local node since connectivity it per node not per cluster.

@xiang90 xiang90 closed this as completed May 17, 2016
@xiang90
Copy link
Contributor

xiang90 commented May 17, 2016

If you are talking about actual cluster events like remove/add nodes, there is already an issue for it :#5277

@celevra
Copy link
Author

celevra commented May 17, 2016

Thanks for the answer 
If Polling for /health is the right way how fast can I do it without disturbing etcd? Every 2 seconds?


Von: Xiang Li [email protected]
Gesendet: 17.05.2016 4:58 vorm.
An: coreos/etcd
Cc: Philipp Zeitschel; Author
Betreff: Re: [coreos/etcd] Question: how to watch for cluster events? (#5357)

If you are talking about actual cluster events like remove/add nodes, there is already an issue for it :#5277


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

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

No branches or pull requests

2 participants