Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

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

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

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

gkleiman opened this issue Aug 14, 2015 · 0 comments
Assignees
@gkleiman
Labels
bug

Comments

@gkleiman
Copy link
Member

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
Fixes #520 - fetch the frameworkId from the state store on MesosDrive…
3359ad5 
…r creation
@gkleiman gkleiman changed the title Chronos sometimes uses an empty frameworkId on a leader fail over 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
Fixes #520 - fetch the frameworkId from the state store on MesosDrive…
ef0976a 
…r creation
gkleiman added a commit that referenced this issue Aug 18, 2015
@gkleiman
Fixes #520 - fetch the frameworkId from the state store on MesosDrive…
d2905db 
…r creation
gkleiman added a commit that referenced this issue Aug 18, 2015
@gkleiman
Merge pull request #521 from mesos/gk/fix_520
a6e6d93 
Fixes #520 - fetch the frameworkId from the state store on MesosDriver creation
@gkleiman gkleiman mentioned this issue Aug 24, 2015
Open
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@gkleiman gkleiman

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gkleiman