Yusaku Sako created AMBARI-15005:
------------------------------------
Summary: 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
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)
