Details
-
Bug
-
Status: Accepted
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
If a framework reregisters with a new user, the master would ignore the user update because of MESOS-703:
https://github.com/apache/mesos/blob/f1dc50568dcc90cec7158205dca86a2398a42dcd/src/master/framework.cpp#L526-L529
However, it would send the framework info coming from the framework (i.e., with the new user) provided by the framework to all agents:
https://github.com/apache/mesos/blob/f1dc50568dcc90cec7158205dca86a2398a42dcd/src/master/master.cpp#L2748-L2757
https://github.com/apache/mesos/blob/f1dc50568dcc90cec7158205dca86a2398a42dcd/src/master/master.cpp#L3156-L3162
But, when an agent reregistered, the master would send the framework info from its in-memory state:
https://github.com/apache/mesos/blob/f1dc50568dcc90cec7158205dca86a2398a42dcd/src/master/master.cpp#L7827-L7842
This would make the framework info inconsistent between the master and some of its agents. Although it won't affect executor and task launch (as the framework info would be injected into RunTask(Group)*Message), if there is a master failover, a race between framework and agent reregistrations would make the new master learn different framework info.