You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bernd Mathiske (JIRA)" <ji...@apache.org> on 2014/08/02 01:25:40 UTC

[jira] [Updated] (MESOS-1630) Remove framework from completedFrameworks if framework re-registers.

     [ https://issues.apache.org/jira/browse/MESOS-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bernd Mathiske updated MESOS-1630:
----------------------------------

    Shepherd: Benjamin Hindman

> 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)