You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Brenden Matthews (JIRA)" <ji...@apache.org> on 2013/08/06 20:57:47 UTC

[jira] [Commented] (MESOS-616) The Master / Slave should not store frameworks as both active and completed.

    [ https://issues.apache.org/jira/browse/MESOS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731103#comment-13731103 ] 

Brenden Matthews commented on MESOS-616:
----------------------------------------

How about something like this:

https://github.com/airbnb/mesos/commit/4b5cf396bdf9a6852e65a8243246c126b7755557

It's a bit messy because the framework is a shared_ptr in `completedFrameworks`, but not in `frameworks`.  There's no way to release ownership of a boost::shared_ptr without messing about.
                
> The Master / Slave should not store frameworks as both active and completed.
> ----------------------------------------------------------------------------
>
>                 Key: MESOS-616
>                 URL: https://issues.apache.org/jira/browse/MESOS-616
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Benjamin Mahler
>            Assignee: Benjamin Mahler
>
> Currently the Master and Slave move frameworks into a 'completed' buffer once they disconnect from the Master / are no longer running tasks on the Slave.
> When the framework becomes active once again, it is not removed from the 'completed' buffer in both the Master and the Slave. Moving out of completed when it becomes active will simplify the webui, as it currently has to deal with a framework possibly being considered both active and completed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira