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

Scheduler driver re-registration backoff #15

Open
tarnfeld opened this issue Jan 22, 2015 · 2 comments
Open

Scheduler driver re-registration backoff #15

tarnfeld opened this issue Jan 22, 2015 · 2 comments

Comments

@tarnfeld
Copy link
Contributor

MESOS-1903 was implemented and is due to come out in 0.22.0 so when Pesos supposed re-registration we should probably do something similar.

@wickman
Copy link
Owner

wickman commented Mar 28, 2015

Implemented at a835b12. Please take a look.

@tarnfeld
Copy link
Contributor Author

I was doing some testing locally and there seems to be a bug relating to when a master disconnection happens. It appears the re-registration loop is never started.

For example, after the first registration, the next tick on the loop effectively disables the backoff and from what I can tell in the event of a master disconnection, it isn't re-enabled.

Perhaps I'm missing something, or maybe I didn't wait long enough for the framework to pick up the error. I doing a simple test with the standalone master detector and stopping/starting the same master a few times.

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

2 participants