[
https://issues.apache.org/jira/browse/YARN-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938225#comment-14938225
]
Anubhav Dhoot commented on YARN-3996:
-------------------------------------
SchedulerUtils has multiple overloads of normalizeRequests. The ones that take
in increment and min handle what you are looking to do.
Fair has support for the increment and Fifo/Capacity do not. So Fair does
multiple of increment and uses min for min while Fifo/Capacity does multiple of
min and use min for min. Basically Capacity/Fifo are setting incr also to min.
We need to do the same in RMAppManager.
That way Fair can continue supporting zero min and use multiple of incr and
Fifo/Capacity can choose to not support zero min and support multiple of min.
> 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: Neelesh Srinivas Salian
> 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)
