ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15005) Ambari Server upgrade makes unwanted changes to capacity-scheduler.xml
Date Sun, 06 Mar 2016 21:44:40 GMT

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

Hudson commented on AMBARI-15005:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.2 #476 (See [https://builds.apache.org/job/Ambari-branch-2.2/476/])
AMBARI-15005. Ambari Server upgrade makes unwanted changes to (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=61c1007df1abadcb9891d15c8a3396be539add29])
* ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/configuration/capacity-scheduler.xml
* ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/capacity-scheduler.xml


> 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: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.2.2
>
>         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)

Mime
View raw message