----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/44394/#review122106 -----------------------------------------------------------
Ship it! Ship It! - Dmitro Lisnichenko On March 4, 2016, 5:53 p.m., Vitalyi Brodetskyi wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/44394/ > ----------------------------------------------------------- > > (Updated March 4, 2016, 5:53 p.m.) > > > Review request for Ambari and Dmitro Lisnichenko. > > > Bugs: AMBARI-15005 > https://issues.apache.org/jira/browse/AMBARI-15005 > > > Repository: ambari > > > 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. > > > Diffs > ----- > > > ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/capacity-scheduler.xml > 6c21848 > > ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/configuration/capacity-scheduler.xml > bac8c52 > > Diff: https://reviews.apache.org/r/44394/diff/ > > > Testing > ------- > > mvn clean test > > > Thanks, > > Vitalyi Brodetskyi > >
