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 "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2015/07/31 10:49:05 UTC

[jira] [Commented] (YARN-3996) YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305

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

Rohith Sharma K S commented on YARN-3996:
-----------------------------------------

CIIAW, SchedulerUtils.normalizeRequests() is being called in allocate() in CS and FS which resourceRequest is normalized(reset) to minimumAllocation. So, it should not be matter for AM container resource Request where normalization is done in RMAppManager. Instead of normalizing at scheduler, here normalization is done at RMAppManager. Does this is impacting?

> YARN-789 (Support for zero capabilities in fairscheduler) is broken after YARN-3305
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-3996
>                 URL: https://issues.apache.org/jira/browse/YARN-3996
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler, fairscheduler
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>            Priority: Critical
>
> RMAppManager#validateAndCreateResourceRequest calls into normalizeRequest with mininumResource for the incrementResource. This causes normalize to return zero if minimum is set to zero as per YARN-789



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