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.

Sign up for GitHub

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

Jump to bottom

Marathon uses new framework ID after failover #1063

Closed
drexin opened this issue Jan 21, 2015 · 0 comments
Closed

Marathon uses new framework ID after failover #1063

drexin opened this issue Jan 21, 2015 · 0 comments
Assignees
@drexin
Milestone
0.8.0

Comments

@drexin
Copy link
Contributor

drexin commented Jan 21, 2015

When the instance that gets newly elected has been online before the first leader stored the framework ID in zookeeper, it uses a new one.
@drexin drexin self-assigned this Jan 21, 2015
@drexin drexin added this to the 0.8.0 milestone Jan 21, 2015
@drexin drexin closed this as completed in ae64e82 Jan 21, 2015
ConnorDoyle added a commit that referenced this issue Jan 21, 2015
@ConnorDoyle
Merge pull request #1064 from mesosphere/wip-1063-drexin
4f792e2 
fixes #1063 and #793 - Always fetch current framework ID in MarathonSche...
@nqn nqn mentioned this issue Mar 17, 2015
Closed
16 tasks
@mesosphere mesosphere locked and limited conversation to collaborators Mar 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@drexin drexin

Labels
None yet
Projects
None yet
Milestone
0.8.0
Development

No branches or pull requests
1 participant
@drexin