[
https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613575#comment-15613575
]
Ray Chiang commented on YARN-2876:
----------------------------------
Another quick note. With this patch applied to trunk, I get consistent test
failures:
Failed tests:
TestFairScheduler.testChildMaxResources:504 App 1 is not running with the
correct number of containers expected:<2> but was:<3>
TestFairScheduler.testMoveWouldViolateMaxResourcesConstraints Expected
exception: org.apache.hadoop.yarn.exceptions.YarnException
> In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for
> subqueues
> ------------------------------------------------------------------------------------
>
> Key: YARN-2876
> URL: https://issues.apache.org/jira/browse/YARN-2876
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler, resourcemanager
> Reporter: Siqi Li
> Assignee: Siqi Li
> Labels: oct16-easy
> Attachments: YARN-2876.v1.patch, YARN-2876.v2.patch,
> YARN-2876.v3.patch, YARN-2876.v4.patch, screenshot-1.png
>
>
> If a subqueue doesn't have a maxResource set in fair-scheduler.xml, JMX and
> Scheduler UI will display the entire cluster capacity as its maxResource
> instead of its parent queue's maxResource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
