
Loading…
Chronos sometimes registers using an empty frameworkId after a leader fail over #520
Closed
gkleiman opened this Issue
· 0 comments
Collaborator
gkleiman
commented
|
|
gkleiman |
Fixes #520 - fetch the frameworkId from the state store on MesosDrive…
…
…r creation |
3359ad5
|
|
|
gkleiman |
Fixes #520 - fetch the frameworkId from the state store on MesosDrive…
…
…r creation |
ef0976a
|
|
|
gkleiman |
Fixes #520 - fetch the frameworkId from the state store on MesosDrive…
…
…r creation |
d2905db
|
|
|
gkleiman |
Fixes #520 - fetch the frameworkId from the state store on MesosDrive…
…
…r creation |
0fa97da
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.