[jira] [Commented] (MESOS-2676) slave recovery always fails when resources change

["Joe Smith (JIRA)" <ji...@apache.org>]

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

Joe Smith commented on MESOS-2676:
----------------------------------

[~vinodkone] made [a compelling explanation previously|http://mail-archives.apache.org/mod_mbox/mesos-user/201406.mbox/%3CCAAkWvAzphphzFHNBr46AmFXWg3bynPPbn+jL4wC8qpoR9CsGfw@mail.gmail.com%3E]- but I don't think we should let this go.

What if the resources increase by (for example) 1.0 CPU? Surely that's a "safe" change, and allowing changes of some nature would greatly increase the flexibility of operators.

> slave recovery always fails when resources change
> -------------------------------------------------
>
>                 Key: MESOS-2676
>                 URL: https://issues.apache.org/jira/browse/MESOS-2676
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: David Robinson
>
> Slave recovery fails whenever --resources is changed. Ideally recovery would only fail if --resources has changed _and_ the still-executing tasks no longer fit within the new --resources range. Increasing resources should always be allowed. For example, if a slave was started with --resources=cpus:15, then the slave was restarted w/ --resources=cpus:16, the slave should start successfully. Same for mem, ports, disk and ephemeral_ports.



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