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

Chronos sometimes registers using an empty frameworkId after a leader fail over #520

Closed
gkleiman opened this Issue Aug 14, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@gkleiman
Member

gkleiman commented Aug 14, 2015

After the network partition it has been observed (#511) that the initial Chronos leader fails over as expected, but the new Chronos leader does a registration with an empty frameworkId, instead of using the frameworkId obtained by the initial leader.

This results in a registration instead of a re-registration.

@gkleiman gkleiman added the bug label Aug 14, 2015

@gkleiman gkleiman self-assigned this Aug 14, 2015

gkleiman added a commit that referenced this issue Aug 14, 2015

@gkleiman gkleiman changed the title from Chronos sometimes uses an empty frameworkId on a leader fail over to Chronos sometimes registers using an empty frameworkId after a leader fail over Aug 14, 2015

gkleiman added a commit that referenced this issue Aug 17, 2015

gkleiman added a commit that referenced this issue Aug 18, 2015

@gkleiman gkleiman closed this in 0fa97da Aug 18, 2015

gkleiman added a commit that referenced this issue Aug 18, 2015

Merge pull request #521 from mesos/gk/fix_520
Fixes #520 - fetch the frameworkId from the state store on MesosDriver creation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment