[ https://issues.apache.org/jira/browse/MESOS-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085702#comment-14085702 ]
Vinod Kone commented on MESOS-1630: ----------------------------------- Hey [~bernd-mesos]. I was thinking more along the lines of what to do at step 3). When a framework with an "id" attempts to re-register and there is already a "completed" framework with the same id, move the completed framework to active frameworks. After this, step 5) doesn't seem necessary. I haven't looked at the master's code to confirm if there is anything else that needs to be done. > Remove framework from completedFrameworks if framework re-registers. > -------------------------------------------------------------------- > > Key: MESOS-1630 > URL: https://issues.apache.org/jira/browse/MESOS-1630 > Project: Mesos > Issue Type: Bug > Components: master > Affects Versions: 0.14.0, 0.14.1, 0.14.2, 0.17.0, 0.16.0, 0.15.0, 0.18.0, > 0.18.1, 0.18.2, 0.19.0, 0.19.1 > Reporter: Benjamin Hindman > Assignee: Bernd Mathiske > Priority: Critical > > If a framework gets removed, for example, because it unregisters with the > master (i.e., due to MESOS-1550), but then the same framework ID is reused > when a framework re-registers (which we currently allow) then we should > remove the framework from Master::completedFrameworks otherwise when a slave > re-registers then in Master::reconcile we'll notice that the slave is > runnings tasks from a completed framework and tell the slave to shutdown that > framework, thus shutting down all of the tasks. > This should be easily fixed by removing the framework from > completedFrameworks when a framework re-registers with the same ID as a > completed framework. -- This message was sent by Atlassian JIRA (v6.2#6252)