On 2008-03-10 23:37:36 -0400, [EMAIL PROTECTED] wrote:
> I can leave the cluster running for hours and this slave will never
> "register" itself with the namenode. I've been messing with this problem
> for three days now and I'm out of ideas. Any suggestions?
I had a similar-sounding problem with a 0.16.0 setup I had...
namenode thinks datanodes are dead, but the datanodes complain if
namenode is unreachable so there must be *some* connectivity.
Admittedly I haven't had the time yet to recreate what I did to see if
I had just mangled some config somewhere, but I was eventually able to
sort out my problem by...and yes, this sounds a bit wacky... running
a given datanode interactively, suspending it, then bringing it back
to the foreground. E.g. (assuming your namenode is already running):
$ bin/hadoop datanode
<ctrl-Z>
$ fg
and the datanode then magically registered with the namenode.
Give it a shot... I'm curious to hear if it works for you, too.
-Coyle
