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

Posted to issues@mesos.apache.org by "Gilbert Song (JIRA)" <ji...@apache.org> on 2016/05/26 23:28:12 UTC

[jira] [Updated] (MESOS-5464) The max number of completed executors for a mesos slave should be configurable

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

Gilbert Song updated MESOS-5464:
--------------------------------
    Assignee: Kevin Devroede

> The max number of completed executors for a mesos slave should be configurable
> ------------------------------------------------------------------------------
>
>                 Key: MESOS-5464
>                 URL: https://issues.apache.org/jira/browse/MESOS-5464
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Kevin Johnstone
>            Assignee: Kevin Devroede
>            Priority: Trivial
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The number of completed executors per framework should be configurable. Frameworks such as Chronos make one executor per tasks and the default of 150 executors makes sandbox logs inaccessible through the mesos UI very quickly, far before the specified timeout for garbage collection for a task. https://github.com/apache/mesos/blob/4db9b630cc67f706a8814436309ab589cbaa64fc/src/slave/constants.hpp#L64 shows where the constant is currently set.



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