Member since
10-26-2017
14
Posts
0
Kudos Received
0
Solutions
11-23-2017
05:18 PM
@Aditya Sirna Changing the ResourceManager , NodeManager, Timeline service address to proper hostnames instead of localhost worked. Thanks a lot. Nirmal J
... View more
11-23-2017
04:20 PM
@Aditya Sirna This lists no nodes. yarn node -list 17/11/23 16:19:24 INFO impl.TimelineClientImpl: Timeline service address: http://localhost:8188/ws/v1/timeline/ 17/11/23 16:19:24 INFO client.RMProxy: Connecting to ResourceManager at localhost/127.0.0.1:8050 17/11/23 16:19:24 INFO client.AHSProxy: Connecting to Application History server at localhost/127.0.0.1:10200 Total Nodes:0 Node-Id Node-StateNode-Http-AddressNumber-of-Running-Containers
... View more
11-23-2017
03:14 PM
@Aditya Sirna Thanks for your quick response. But the node managers are all up and running Please find attached the screenshotsscreen-shot-2017-11-23-at-84336-pm.pngscreen-shot-2017-11-23-at-84200-pm.png Thanks, Nirmal J
... View more
11-23-2017
12:21 PM
Hello, I tried to submit a spark job using YARN. But the application state remains UNDEFINED with the below error. "ACCEPTED: waiting for AM container to be allocated, launched and register with RM." When I checked the node status, the number of active nodes=0 and total memory=0. Is it because the datanodes are not detected by namenode? When I checked the Name Node UI, it shows two data node information. Please find attached the screen shots Could anyone please help me to resolve this. Thanks, Nirmal J screen-shot-2017-11-23-at-54836-pm.pngscreen-shot-2017-11-23-at-54419-pm.pngscreen-shot-2017-11-23-at-54352-pm.png
... View more
Labels:
- Labels:
-
Apache YARN
-
Cloudera Manager
10-27-2017
10:36 AM
Thanks a lot @Jay SenSharma This fixed the issue. Thanks again for your time
... View more
10-27-2017
09:31 AM
@Jay SenSharma Please find attached the core-ste.xml and hdfs-site.xml and /etc/hosts in all nodes hosts-master.txthosts-slave-1.txthosts-slave-2.txtcore-site.xmlhdfs-site.xml Thanks, Nirmal J
... View more
10-27-2017
08:32 AM
@Jay SenSharma [cloudbreak@ip-10-0-223-116 ~]$ sudo service iptables status iptables: Firewall is not running. [cloudbreak@ip-10-0-223-116 ~]$ hostname -f ip-10-0-223-116.ec2.internal [cloudbreak@ip-10-0-223-116 ~]$ sudo netstat -tnlpa | grep `cat /var/run/hadoop/hdfs/hadoop-hdfs-namenode.pid` tcp00 127.0.0.1:80200.0.0.0:* LISTEN29280/java tcp00 127.0.0.1:50070 0.0.0.0:* LISTEN29280/java tcp00 127.0.0.1:20103 0.0.0.0:* LISTEN29280/java
... View more
10-27-2017
08:29 AM
This didn't work @Aditya Sirna. Still the same issue. It seems like some kind of firewall issue. telnet 10.0.223.116 8020 is connecting from namenode, but not from datanode
... View more
10-27-2017
07:23 AM
@Aditya Sirna The error seems to be weird 1) The namenode service is up and running in the master [cloudbreak@ip-10-0-223-116 ~]$ sudo netstat -nltp| grep :8020 tcp00 127.0.0.1:80200.0.0.0:* LISTEN6689/java 2) Port 8020 is open for allscreen-shot-2017-10-27-at-124602-pm.png 3) I can ping from master to slave using the private DNS 4) But telnet is getting connection refused [cloudbreak@ip-10-0-109-247 hdfs]$ telnet 10.0.223.116 8020 Trying 10.0.223.116... telnet: connect to address 10.0.223.116: Connection refused 5) Datanode logs has the below error 2017-10-27 05:24:15,073 INFOipc.Client (Client.java:handleConnectionFailure(906)) - Retrying connect to server: ip-10-0-223-116.ec2.internal/10.0.223.116:8020. Already tried 48 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50, sleepTime=1000 MILLISECONDS)
... View more
10-27-2017
04:07 AM
@Aditya Sirna I tried to give the namenode public IP there. But the namenode itself failed to start Call From ip-10-0-65-59.ec2.internal/10.0.65.59 to 34.231.98.121:8020 failed on connection exception: java.net.ConnectException: Connection refused;
... View more