[AMBARI-15005] Ambari Server upgrade makes unwanted changes to capacity-scheduler.xml

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2.1
• Fix Version/s: 2.2.2
• Component/s: ambari-server
• Assignee: Vitaly Brodetskyi
• Reporter: Yusaku Sako
• Created: 11/Feb/16 03:36
• Updated: 06/Mar/16 22:06
• Resolved: 06/Mar/16 19:55

Description

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:

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

This is probably because Ambari Server on upgrade adds default properties that are missing from the existing configs.

Issue Links

• links to: review request