hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4067) available resource could be set negative
Date Sun, 20 Mar 2016 18:04:33 GMT

    [ https://issues.apache.org/jira/browse/YARN-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203401#comment-15203401

Karthik Kambatla commented on YARN-4067:

IMO, available resource being negative is misleading. Even if we overcommit resources, it
needs to transparent to users. This is actually one of the goals of YARN-1011. 

With regards to YARN-291, I was under the impression the primary motive of that work was to
allow modifying the capacity of nodes dynamically. When the capacity is reduced on a fully
allocated node, we should handle it more gracefully. Per YARN-1011 parlance, we should demote
these containers to being called opportunistic. Sometimes, this might not be possible/allowed
and the capacity update should fail. We can discuss this more on YARN-291. 

> available resource could be set negative
> ----------------------------------------
>                 Key: YARN-4067
>                 URL: https://issues.apache.org/jira/browse/YARN-4067
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.1
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: YARN-4067.patch
> as mentioned in YARN-4045 by [~leftnoteasy], available memory could be negative due to
reservation, propose to use componentwiseMax to updateQueueStatistics in order to cap negative
value to zero

This message was sent by Atlassian JIRA

View raw message