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

Carlo Curino commented on YARN-5165:
------------------------------------

The fix in {{TestSimpleCapacityReplanner}} is due to the fact that the previous 
policy was relying on the {{DefaultResourceCalculator}} (which ignores 
{{vcores}} in the calculations), and so we had missed a misconfiguration of the 
{{vcores}} in the inital plan. The test should have failed. The new code 
proposed in this patch, caught the issue, hence the test fix.

> NoOvercommitPolicy does not take advantage of RLE representation of plan
> ------------------------------------------------------------------------
>
>                 Key: YARN-5165
>                 URL: https://issues.apache.org/jira/browse/YARN-5165
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, fairscheduler, resourcemanager
>            Reporter: Carlo Curino
>            Assignee: Carlo Curino
>         Attachments: YARN-5165.1.patch, YARN-5165.2.patch, YARN-5165.3.patch
>
>
> As a consequence small time granularities (e.g., 1 sec) and long time horizon 
> for a reservation (e.g., months) run rather slow (10 sec). 
> Proposed resolution is to switch to interval math in checking, similar to how 
> YARN-4359 does for agents.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to