[
https://issues.apache.org/jira/browse/MESOS-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101911#comment-14101911
]
Adam B commented on MESOS-1630:
-------------------------------
+1 to closing this in favor of 1219+1719. A completed framework should not be
able to reregister with the same frameworkID. I might prefer to see the master
return a new frameworkID for a completed framework's reregistration, but a
rejection can easily be used to trigger a reregistration without a frameworkID.
> 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::frameworks.completed otherwise when a slave
> re-registers then in Master::reconcile we'll notice that the slave is running
> 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
> frameworks.completed when a framework re-registers with the same ID as a
> completed framework.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
