-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34451/
-----------------------------------------------------------
(Updated May 20, 2015, 3:10 a.m.)
Review request for Ambari, Andrew Onischuk, Dmitro Lisnichenko, Jonathan
Hurley, Nate Cole, 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 (updated)
-----
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
e954af2
ambari-server/src/main/resources/stacks/HDP/2.3.GlusterFS/services/YARN/configuration/capacity-scheduler.xml
63d56b0
ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/capacity-scheduler.xml
PRE-CREATION
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
