You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2014/10/29 01:08:34 UTC

[jira] [Resolved] (MESOS-631) Slave started in cleanup mode shouldn't accept new tasks

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

Vinod Kone resolved MESOS-631.
------------------------------
       Resolution: Fixed
    Fix Version/s: 0.21.0

Fixed as part of status updates refactor.

commit e64dda411bc83963179c92ae71caefa8d21b54b4
Author: Vinod Kone <vi...@gmail.com>
Date:   Wed Oct 15 18:22:46 2014 -0700

    Updated status update manager to forward updates via slave.
    
    Review: https://reviews.apache.org/r/26846


> Slave started in cleanup mode shouldn't accept new tasks
> --------------------------------------------------------
>
>                 Key: MESOS-631
>                 URL: https://issues.apache.org/jira/browse/MESOS-631
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>              Labels: twitter
>             Fix For: 0.21.0
>
>
> Since a slave shuts down after getting acks for all the old pending updates, there is no point in accepting more tasks. We can achieve this simply by having the slave to not register with the master.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)