You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sudhir Prakash (JIRA)" <ji...@apache.org> on 2014/05/21 22:02:37 UTC

[jira] [Commented] (AMBARI-5847) Nodemanager is running on nodes that were not chosen during installation

    [ https://issues.apache.org/jira/browse/AMBARI-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005156#comment-14005156 ] 

Sudhir Prakash commented on AMBARI-5847:
----------------------------------------

I noticed that immediately after the install, Nodemanger is started on the correct nodes. However, nodemanager is configured to start on boot on ALL nodes. So after rebooting nodes, Nodemanager is running on aLL nodes.

> Nodemanager is running on nodes that were not chosen during installation
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-5847
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5847
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>         Environment: SLES11
> 7 Node cluster (2 master, 4 data, 1 edge)
> Ambari 1.6.0-39
>            Reporter: Sudhir Prakash
>
> I performed an installation using the Ambari GUI and chose to install Nodemanger only on my 4 Datanodes. However, when I do "ps aux | grep nodemanager", I see Nodemanger is running on all 7 of my nodes.
> The Ambari GUI reports that 4/4 Nodemangers are running.
> Example out put from my Master #1 node:
> {code}
> hadoopvm1-1:/var/lib/ambari-server # ps aux | grep nodemanager
> yarn      7289  0.1  0.6 4791064 304496 ?      Sl   May20   1:27 /opt/teradata/jvm64/jdk7/bin/java -Dproc_nodemanager -Xmx4096m -Dhadoop.log.dir=/var/opt/teradata/log/hadoop/yarn/yarn -Dyarn.log.dir=/var/opt/teradata/log/hadoop/yarn/yarn -Dhadoop.log.file=yarn-yarn-nodemanager-hadoopvm1-1.log -Dyarn.log.file=yarn-yarn-nodemanager-hadoopvm1-1.log -Dyarn.home.dir= -Dyarn.id.str=yarn -Dhadoop.root.logger=INFO,RFA -Dyarn.root.logger=INFO,RFA -Djava.library.path=:/usr/lib/hadoop/lib/native/Linux-amd64-64:/usr/lib/hadoop/lib/native:/usr/lib/hadoop/lib/native/Linux-amd64-64:/usr/lib/hadoop/lib/native -Dyarn.policy.file=hadoop-policy.xml -server -Dhadoop.log.dir=/var/opt/teradata/log/hadoop/yarn/yarn -Dyarn.log.dir=/var/opt/teradata/log/hadoop/yarn/yarn -Dhadoop.log.file=yarn-yarn-nodemanager-hadoopvm1-1.log -Dyarn.log.file=yarn-yarn-nodemanager-hadoopvm1-1.log -Dyarn.home.dir=/usr/lib/hadoop-yarn -Dhadoop.home.dir=/usr/lib/hadoop-yarn -Dhadoop.root.logger=INFO,RFA -Dyarn.root.logger=INFO,RFA -Djava.library.path=:/usr/lib/hadoop/lib/native/Linux-amd64-64:/usr/lib/hadoop/lib/native:/usr/lib/hadoop/lib/native/Linux-amd64-64:/usr/lib/hadoop/lib/native -classpath /etc/hadoop/conf:/etc/hadoop/conf:/etc/hadoop/conf:/usr/lib/hadoop/lib/*:/usr/lib/hadoop/.//*:/usr/lib/hadoop-hdfs/./:/usr/lib/hadoop-hdfs/lib/*:/usr/lib/hadoop-hdfs/.//*:/usr/lib/hadoop-yarn/lib/*:/usr/lib/hadoop-yarn/.//*:/usr/lib/hadoop-mapreduce/lib/*:/usr/lib/hadoop-mapreduce/.//*::/usr/share/java/jdbc-mysql.jar:/usr/share/java/mysql-connector-java-5.1.29.jar:/usr/share/java/mysql-connector-java.jar:/usr/lib/hadoop-mapreduce/*:/usr/lib/tez/*:/usr/lib/tez/lib/*:/etc/tez/conf:/usr/share/java/jdbc-mysql.jar:/usr/share/java/mysql-connector-java-5.1.29.jar:/usr/share/java/mysql-connector-java.jar:/usr/lib/hadoop-mapreduce/*:/usr/lib/tez/*:/usr/lib/tez/lib/*:/etc/tez/conf:/usr/lib/hadoop-yarn/.//*:/usr/lib/hadoop-yarn/lib/*:/etc/hadoop/conf/nm-config/log4j.properties org.apache.hadoop.yarn.server.nodemanager.NodeManager
> {code}
> {code}
> hadoopvm1-1:/var/lib/ambari-server # chkconfig --list | grep yarn
> hadoop-yarn-nodemanager   0:off  1:off  2:off  3:on   4:on   5:on   6:off
> hadoop-yarn-proxyserver   0:off  1:off  2:off  3:on   4:on   5:on   6:off
> hadoop-yarn-resourcemanager  0:off  1:off  2:off  3:on   4:on   5:on   6:off
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)