Yes. As vinod pointed in that link, check yarn.resourcemanager.hostname on slave node yarn-site.xml and put your master node hostname there.
On Sun, Jul 13, 2014 at 2:47 PM, Sisu Xi <[email protected]> wrote: > Hi, Ravi: > > Thanks again for your help! > > The website only shows one node. a screenshot is attached. > > I restart the service, on master, it says: > xisisu@master:/usr/local/hadoop$ jps > 15862 Jps > 15570 NodeManager > 15461 ResourceManager > 15149 DataNode > 15025 NameNode > > on slave, it says: > xisisu@slave-01:/usr/local/hadoop$ jps > 19752 DataNode > 19859 NodeManager > 20003 Jps > > I also checked the yarn log on the slave node, seems it cannot connect to > the server, > xisisu@slave-01:/usr/local/hadoop$ tail > logs/yarn-xisisu-nodemanager-slave-01.log > 2014-07-13 14:41:35,947 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 0 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:36,947 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 1 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:37,961 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 2 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:38,962 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 3 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:39,962 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 4 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:40,963 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 5 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:41,963 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 6 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:42,963 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 7 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:43,964 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 8 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > 2014-07-13 14:41:44,964 INFO org.apache.hadoop.ipc.Client: Retrying > connect to server: 0.0.0.0/0.0.0.0:8031. Already tried 9 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > > > I googled and found this: > > http://hortonworks.com/community/forums/topic/retrying-connect-to-server-0-0-0-00-0-0-08030/ > > Seems it is the configuration error? > > Thanks very much! > > Sisu > > > > > > > On Sun, Jul 13, 2014 at 2:33 PM, Ravi Mutyala <[email protected]> > wrote: > >> http://localhost:8088/cluster/nodes > > > > > > -- > > > *Sisu Xi, PhD Candidate* > > http://www.cse.wustl.edu/~xis/ > Department of Computer Science and Engineering > Campus Box 1045 > Washington University in St. Louis > One Brookings Drive > St. Louis, MO 63130 > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
