I believe the datanode is the same physical machine as the namenode if I understand this problem correctly. Which really puts pay to our suggestions about traceroute and firewalls)
I have one question, is the ip address consistent, I think in one of the thread mails, it was stated that the ip address sometimes changes. That may be because the dns lookup to the primary server timed out and the secondary returned a different address, or some other floating dns oddity, and that could be a part of the problem. We had problems with transient dns failures at one point on one of our larger clusters, and just hardcoded the ip addresses after that. On Wed, Apr 22, 2009 at 8:03 PM, Raghu Angadi <rang...@yahoo-inc.com> wrote: > Stas Oskin wrote: > >> >> Tried in step 3 to telnet both the 50010 and the 8010 ports of the >> problematic datanode - both worked. >> > > Shouldn't you be testing connecting _from_ the datanode? The error you > posted is while this DN is trying connect to another DN. > > Raghu. > > > I agree there is indeed an interesting problem :). Question is how it can >> be >> solved. >> >> Thanks. >> >> > -- Alpha Chapters of my book on Hadoop are available http://www.apress.com/book/view/9781430219422
