[
https://issues.apache.org/jira/browse/AMBARI-15005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180508#comment-15180508
]
Hadoop QA commented on AMBARI-15005:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791483/AMBARI-15005.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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5733//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5733//console
This message is automatically generated.
> Ambari Server upgrade makes unwanted changes to capacity-scheduler.xml
> ----------------------------------------------------------------------
>
> Key: AMBARI-15005
> URL: https://issues.apache.org/jira/browse/AMBARI-15005
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: Yusaku Sako
> Assignee: Sumit Mohanty
> Priority: Critical
> Attachments: AMBARI-15005.patch
>
>
> Upgraded Ambari Server from 2.1.2.1 to 2.2.1.
> capacity-scheduler.xml prior to upgrade intentionally did not have the
> default queue (per the customer's requirement).
> Ambari automatically added the following, which is unwanted:
> {noformat}
> yarn.scheduler.capacity.default.minimum-user-limit-percent=100
> yarn.scheduler.capacity.root.default.acl_administer_jobs=*
> yarn.scheduler.capacity.root.default.acl_submit_applications=*
> yarn.scheduler.capacity.root.default.capacity=100
> yarn.scheduler.capacity.root.default.maximum-capacity=100
> yarn.scheduler.capacity.root.default.state=RUNNING
> yarn.scheduler.capacity.root.default.user-limit-factor=1
> {noformat}
> This is probably because Ambari Server on upgrade adds default properties
> that are missing from the existing configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
