You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2017/02/17 20:26:41 UTC

[jira] [Commented] (MESOS-7137) Custom executors cannot use any reserved resources.

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

Anand Mazumdar commented on MESOS-7137:
---------------------------------------

{noformat}
commit 267d719c7a8308e1a1b98c73f5091dbb7708c444
Author: Anand Mazumdar <an...@apache.org>
Date:   Fri Feb 17 12:15:54 2017 -0800

    Fixed a bug around executor not able to use reserved resources.

    We were not unallocating the resources before checking if the
    executor resources were contained in the checkpointed resources
    on the agent.

    Review: https://reviews.apache.org/r/56778/
{noformat}

> Custom executors cannot use any reserved resources.
> ---------------------------------------------------
>
>                 Key: MESOS-7137
>                 URL: https://issues.apache.org/jira/browse/MESOS-7137
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Anand Mazumdar
>            Assignee: Anand Mazumdar
>            Priority: Blocker
>              Labels: mesosphere
>
> A custom executor or the built-in default executor cannot launch a task if they use reserved resources as part of {{ExecutorInfo}}. This mostly happens due to the fact that we don't unallocate the {{Resource}} when comparing it with the checkpointed resources on the agent:
> {code}
>   Resources checkpointedExecutorResources =
>     Resources(executorInfo.resources()).filter(needCheckpointing);
> {code}
> The fix can be as simple as changing this to:
> {code}
>   Resources checkpointedExecutorResources =
>     unallocated(executorInfo.resources()).filter(needCheckpointing);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)