Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.2.1
-
None
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.
Attachments
Attachments
Issue Links
- links to