You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Jaimin Jetly <ja...@hortonworks.com> on 2014/05/22 02:55:46 UTC
Review Request 21797: AMBARI-5847. Nodemanager is running on nodes that were
not chosen during installation
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/21797/
-----------------------------------------------------------
Review request for Ambari, Mahadev Konar and Yusaku Sako.
Bugs: AMBARI-5847
https://issues.apache.org/jira/browse/AMBARI-5847
Repository: ambari
Description
-------
This issue happens because we are installing hadoop-yarn-nodemnager, hadoop-yarn-resroucemnaager, hadoop-yarn-proxyserver as part of our rpm install on a host that has any component and hadoop-mapreduce-historyserver on any MapReduce2 component. These rpms are init.d scripts which have chkconfig on and enabled. This causes NodeManagers to come up on hosts where the user chose yarn client on a reboot.
Diffs
-----
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/metainfo.xml 3d3ecc2
ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/YARN/metainfo.xml 5e38538
ambari-server/src/main/resources/stacks/HDP/2.1/services/YARN/metainfo.xml fa8c596
Diff: https://reviews.apache.org/r/21797/diff/
Testing
-------
Tested the patch on the cluster
Thanks,
Jaimin Jetly
Re: Review Request 21797: AMBARI-5847. Nodemanager is running on nodes that
were not chosen during installation
Posted by Mahadev Konar <ma...@apache.org>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/21797/#review43692
-----------------------------------------------------------
Ship it!
Ship It!
- Mahadev Konar
On May 22, 2014, 12:55 a.m., Jaimin Jetly wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/21797/
> -----------------------------------------------------------
>
> (Updated May 22, 2014, 12:55 a.m.)
>
>
> Review request for Ambari, Mahadev Konar and Yusaku Sako.
>
>
> Bugs: AMBARI-5847
> https://issues.apache.org/jira/browse/AMBARI-5847
>
>
> Repository: ambari
>
>
> Description
> -------
>
> This issue happens because we are installing hadoop-yarn-nodemnager, hadoop-yarn-resroucemnaager, hadoop-yarn-proxyserver as part of our rpm install on a host that has any component and hadoop-mapreduce-historyserver on any MapReduce2 component. These rpms are init.d scripts which have chkconfig on and enabled. This causes NodeManagers to come up on hosts where the user chose yarn client on a reboot.
>
>
> Diffs
> -----
>
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/metainfo.xml 3d3ecc2
> ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/YARN/metainfo.xml 5e38538
> ambari-server/src/main/resources/stacks/HDP/2.1/services/YARN/metainfo.xml fa8c596
>
> Diff: https://reviews.apache.org/r/21797/diff/
>
>
> Testing
> -------
>
> Tested the patch on the cluster
>
>
> Thanks,
>
> Jaimin Jetly
>
>