Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Hadoop >> mail # user >> Fully distributed hdfs problem 0 live node


Copy link to this message
-
Fully distributed hdfs problem 0 live node
Hi,
I just deployed an three datanodes cluster. But there is a problem that the
live nodes are always 0. There is no datanode connected to the namenode.
Does anybody know why?

Datenode keeps logging the following:

2010-03-16 19:41:50,379 INFO org.apache.hadoop.ipc.RPC: Server at
ubtserver01/xx.xx.xx.xx:54310 not available yet, Zzzzz...
2010-03-16 19:41:52,396 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: ubtserver01/xx.xx.xx.xx6:54310. Already tried 0 time(s).
2010-03-16 19:41:53,405 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: ubtserver01/xx.xx.xx.xx:54310. Already tried 1 time(s).
2010-03-16 19:41:54,410 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: ubtserver01/xx.xx.xx.xx:54310. Already tried 2 time(s).
2010-03-16 19:41:55,414 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: ubtserver01/xx.xx.xx.xx:54310. Already tried 3 time(s).
2010-03-16 19:41:56,416 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: ubtserver01/xx.xx.xx.xx:54310. Already tried 4 time(s).
2010-03-16 19:41:57,422 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: ubtserver01/xx.xx.xx.xx:54310. Already tried 5 time(s).
2010-03-16 19:41:58,424 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: ubtserver01/xx.xx.xx.xx:54310. Already tried 6 time(s).
2010-03-16 19:41:59,427 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: ubtserver01/xx.xx.xx.xx:54310. Already tried 7 time(s).

And the namenode has log as following:
2010-03-16 19:41:00,746 INFO org.apache.hadoop.ipc.Server: IPC Server
Responder: starting
2010-03-16 19:41:00,747 INFO org.apache.hadoop.ipc.Server: IPC Server
listener on 54310: starting
2010-03-16 19:41:00,747 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 0 on 54310: starting
2010-03-16 19:41:00,748 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 1 on 54310: starting
2010-03-16 19:41:00,756 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 9 on 54310: starting
2010-03-16 19:41:00,756 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 2 on 54310: starting
2010-03-16 19:41:00,756 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 3 on 54310: starting
2010-03-16 19:41:00,756 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 4 on 54310: starting
2010-03-16 19:41:00,756 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 6 on 54310: starting
2010-03-16 19:41:00,792 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 5 on 54310: starting
2010-03-16 19:41:00,792 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 7 on 54310: starting
2010-03-16 19:41:00,792 INFO org.apache.hadoop.ipc.Server: IPC Server
handler 8 on 54310: starting

Thanks a lot.
William
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB