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

Posted to yarn-issues@hadoop.apache.org by "Chang Li (JIRA)" <ji...@apache.org> on 2015/09/02 05:27:45 UTC

[jira] [Updated] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

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

Chang Li updated YARN-4105:
---------------------------
    Attachment: YARN-4105.patch

> Capacity Scheduler headroom for DRF is wrong
> --------------------------------------------
>
>                 Key: YARN-4105
>                 URL: https://issues.apache.org/jira/browse/YARN-4105
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: YARN-4105.patch
>
>
> relate to the problem discussed in YARN-1857. But the min method is flawed when we are using DRC. Have run into a real scenario in production where queueCapacity: <memory:1056256, vCores:3750>, qconsumed: <memory:1054720, vCores:361>, consumed: <memory:125952, vCores:170> limit: <memory:214016, vCores:755>.  headRoom calculation returns 88064 where there is only 1536 left in the queue because DRC effectively compare by vcores. It then caused deadlock because RMcontainer allocator thought there is still space for mapper and won't preempt a reducer in a full queue to schedule a mapper. Propose fix with componentwiseMin. 



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