[
https://issues.apache.org/jira/browse/AMBARI-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581583#comment-14581583
]
Hadoop QA commented on AMBARI-11855:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12738982/AMBARI-11855.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/capacity-scheduler.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3138//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3138//console
This message is automatically generated.
> Capacity scheduler view, wrong queue rename behavior
> ----------------------------------------------------
>
> Key: AMBARI-11855
> URL: https://issues.apache.org/jira/browse/AMBARI-11855
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.1.0
> Reporter: Erik Bergenholtz
> Assignee: Erik Bergenholtz
> Fix For: 2.1.0
>
> Attachments: AMBARI-11855.patch
>
>
> Create child queue 'test1' for 'root'
> Create child queue test2 for queue 'test1'
> Should be:
> {noformat}
> root-
> |default
> |test1-
> |test2
> {noformat}
> Now rename test1 to 'testabc'
> Queue is renamed, but test2 child dissapers.
> Export queue configs contains next:
> {code}
> yarn.scheduler.capacity.maximum-am-resource-percent=0.2
> yarn.scheduler.capacity.maximum-applications=10000
> yarn.scheduler.capacity.node-locality-delay=40
> yarn.scheduler.capacity.resource-calculator=org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator
> yarn.scheduler.capacity.root.acl_administer_queue=*
> yarn.scheduler.capacity.root.capacity=100
> yarn.scheduler.capacity.root.queues=default
> yarn.scheduler.capacity.root.accessible-node-labels=*
> yarn.scheduler.capacity.root.default.acl_submit_applications=*
> yarn.scheduler.capacity.root.default.maximum-capacity=100
> yarn.scheduler.capacity.root.default.user-limit-factor=1
> yarn.scheduler.capacity.root.default.state=RUNNING
> yarn.scheduler.capacity.root.default.capacity=100
> yarn.scheduler.capacity.root.default.queues=testabc
> yarn.scheduler.capacity.root.default.accessible-node-labels=
> yarn.scheduler.capacity.root.default.test1.test2.acl_administer_queue=*
> yarn.scheduler.capacity.root.default.test1.test2.acl_submit_applications=*
> yarn.scheduler.capacity.root.default.test1.test2.minimum-user-limit-percent=100
> yarn.scheduler.capacity.root.default.test1.test2.maximum-capacity=0
> yarn.scheduler.capacity.root.default.test1.test2.user-limit-factor=1
> yarn.scheduler.capacity.root.default.test1.test2.state=RUNNING
> yarn.scheduler.capacity.root.default.test1.test2.capacity=0
> yarn.scheduler.capacity.root.default.test1.test2.ordering-policy=fifo
> yarn.scheduler.capacity.root.default.testabc.acl_administer_queue=*
> yarn.scheduler.capacity.root.default.testabc.acl_submit_applications=*
> yarn.scheduler.capacity.root.default.testabc.minimum-user-limit-percent=100
> yarn.scheduler.capacity.root.default.testabc.maximum-capacity=0
> yarn.scheduler.capacity.root.default.testabc.user-limit-factor=1
> yarn.scheduler.capacity.root.default.testabc.state=RUNNING
> yarn.scheduler.capacity.root.default.testabc.capacity=0
> yarn.scheduler.capacity.root.default.testabc.queues=test2
> yarn.scheduler.capacity.root.default.testabc.ordering-policy=fifo
> {code}
> Now save configs and refresh page in browser.
> Queues now displayed as expected, and exported config is also right:
> {code}
> yarn.scheduler.capacity.maximum-am-resource-percent=0.2
> yarn.scheduler.capacity.maximum-applications=10000
> yarn.scheduler.capacity.node-locality-delay=40
> yarn.scheduler.capacity.resource-calculator=org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator
> yarn.scheduler.capacity.root.acl_administer_queue=*
> yarn.scheduler.capacity.root.capacity=100
> yarn.scheduler.capacity.root.queues=default
> yarn.scheduler.capacity.root.accessible-node-labels=*
> yarn.scheduler.capacity.root.default.acl_submit_applications=*
> yarn.scheduler.capacity.root.default.maximum-capacity=100
> yarn.scheduler.capacity.root.default.user-limit-factor=1
> yarn.scheduler.capacity.root.default.state=RUNNING
> yarn.scheduler.capacity.root.default.capacity=100
> yarn.scheduler.capacity.root.default.queues=testabc
> yarn.scheduler.capacity.root.default.accessible-node-labels=
> yarn.scheduler.capacity.root.default.testabc.acl_administer_queue=*
> yarn.scheduler.capacity.root.default.testabc.acl_submit_applications=*
> yarn.scheduler.capacity.root.default.testabc.minimum-user-limit-percent=100
> yarn.scheduler.capacity.root.default.testabc.maximum-capacity=0
> yarn.scheduler.capacity.root.default.testabc.user-limit-factor=1
> yarn.scheduler.capacity.root.default.testabc.state=RUNNING
> yarn.scheduler.capacity.root.default.testabc.capacity=0
> yarn.scheduler.capacity.root.default.testabc.queues=test2
> yarn.scheduler.capacity.root.default.testabc.ordering-policy=fifo
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
