Benno Evers created MESOS-8451:
----------------------------------
Summary: Unhandled Interference between registration and
reregistration code paths
Key: MESOS-8451
URL: https://issues.apache.org/jira/browse/MESOS-8451
Project: Mesos
Issue Type: Bug
Reporter: Benno Evers
Right now, the code paths for agent registration and agent re-registration run
independent of each other, probably on the assumption that re-registration
requires an agent ID from the master which is only given out after successful
registration, so the code paths cannot interfere.
However, it is not so hard to construct some examples where this fails, e.g.
- Agent sends out registration message 1
- Timeout expires, agent sends out registration message 2
- Agent gets registration message 1, updates agent id, is restarted
- Agent send reregistration message 1 after restart
Most likely, a proper solution will require to introduce some kind of counter
or uuid to the (re-)registration messages, which is also required for proper
handling of multiple reregistration messages as described in MESOS-8273.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
