[
https://issues.apache.org/jira/browse/YARN-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936319#comment-14936319
]
Neelesh Srinivas Salian commented on YARN-3996:
-----------------------------------------------
The idea here is:
Scenario:
1) The ResourceRequest can be requesting for a value in memory that is in
between RM_SCHEDULER_MINIMUM_ALLOCATION_MB and
RM_SCHEDULER_INCREMENT_ALLOCATION_MB
Where, let's say, the minimum is set to zero while the increment is 512MB and
the request is 256MB
In such an event, the normalizeRequest() will normalize the request to the
minimum as opposed to the increment which will be 512MB and fulfilling the
request.
a. I think we may have to change the
Resource normalize(
ResourceCalculator calculator, Resource lhs, Resource min,
Resource max, Resource increment)
with a check for Zero requests
But that would more of a core change that I am not too sure to do if it breaks
anything else.
b. The other would be to check the zero requests and add a check in the Fair
and Capacity scheduler code prior to calling SchedulerUtils.normalizeRequests()
Thoughts?
Thank you.
> 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)
