-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34451/#review84443
-----------------------------------------------------------



ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/configuration/capacity-scheduler.xml
<https://reviews.apache.org/r/34451/#comment135707>

    Actually, this will need a config item in the Upgrade Pack for 2.2 -> 2.3


- Alejandro Fernandez


On May 20, 2015, 12:31 a.m., Alejandro Fernandez wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/34451/
> -----------------------------------------------------------
> 
> (Updated May 20, 2015, 12:31 a.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk, Dmitro Lisnichenko, Sumit 
> Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-11257
>     https://issues.apache.org/jira/browse/AMBARI-11257
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> STR:
> Create a cluster with Ambari 2.1.0, at build 1638
> Install HDP 2.3.0.0 at build 2030, with HDFS, MR, YARN, ZK, OOZIE
> Run Yarn Service Check
> Run Oozie Service Check
> 
> The Resource Manager UI shows the apps as waiting for AM to schedule them, 
> and eventually they get killed.
> 
> For Oozie, it is able to launch the MR jobs, but of course, they timeout.
> 
> The problem is that the 
> yarn.scheduler.capacity.root.default-node-label-expression property is set to 
> " " instead of "", and this behavior changed in HDP 2.3, but works in HDP 2.2 
> as well.
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/configuration/capacity-scheduler.xml
>  f1d4b48 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3.GlusterFS/services/YARN/configuration/capacity-scheduler.xml
>  63d56b0 
>   
> ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/YARN/configuration/capacity-scheduler.xml
>  63d56b0 
>   
> ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_1.3_to_2.2.json
>  f1d08b9 
>   
> ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.0_to_2.2.2.json
>  86521d1 
>   
> ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.0_to_2.2.4.json
>  7721c67 
>   
> ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.1_to_2.2.2.json
>  a040268 
>   
> ambari-server/src/main/resources/upgrade/catalog/UpgradeCatalog_2.1_to_2.2.4.json
>  ba2b3d7 
>   ambari-server/src/test/python/stacks/2.0.6/configs/client-upgrade.json 
> aeecb79 
>   ambari-server/src/test/python/stacks/2.0.6/configs/hbase-2.2.json fa48c6d 
>   ambari-server/src/test/python/stacks/2.0.6/configs/hbase-check-2.2.json 
> 88017b5 
>   ambari-server/src/test/python/stacks/2.0.6/configs/hbase-rs-2.2.json 
> 3109b7a 
>   ambari-server/src/test/python/stacks/2.1/configs/client-upgrade.json 
> 1534619 
>   
> ambari-server/src/test/python/stacks/2.2/configs/journalnode-upgrade-hdfs-secure.json
>  3b6a2fa 
>   ambari-server/src/test/python/stacks/2.2/configs/journalnode-upgrade.json 
> 9d8cb39 
>   
> ambari-server/src/test/python/stacks/2.2/configs/pig-service-check-secure.json
>  a7a6121 
>   ambari-server/src/test/python/stacks/2.2/configs/ranger-admin-upgrade.json 
> 3e6307d 
>   
> ambari-server/src/test/python/stacks/2.2/configs/ranger-usersync-upgrade.json 
> caec8ca 
> 
> Diff: https://reviews.apache.org/r/34451/diff/
> 
> 
> Testing
> -------
> 
> Installed ambari-server
> Patched the file capacity-scheduler.xml
> Deployed a cluster with HDP 2.3 and HDFS, YARN, MR, ZK
> Verified the property change in the configs, and that the YARN Service Check 
> passed.
> 
> ----------------------------------------------------------------------
> Total run:741
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Reply via email to