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

Junping Du commented on YARN-4067:
----------------------------------

I don't think we should cap negative value to zero in any case. In some cases, 
YARN provide flexible resource model to allow resource to do over commit. Just 
like OS can claim/allocate more memory resource than physical one - backed by 
virtual memory mechanism, YARN's resource model is also flexible here - backed 
by mechanisms like: resource/container preemption, dynamic resource 
configuration (YARN-291), etc. We never have assumption that available resource 
couldn't be negative value, and this negative value can notify YARN to balance 
resource consumption again in some way. 
Thus, I propose to resolve this JIRA as Not A problem or Invalid.

> 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
(v6.3.4#6332)

Reply via email to