Stas Oskin wrote:
Hi again.
Other tools, like balancer, or the web browsing from namenode, don't work as
well.
This because other nodes complain about not reaching the offending node as
well.
I even tried netcat'ing the IP/port from another node - and it successfully
connected.
Any advice on this "No route to host" error?
"No route to host" generally means machines have routing problems.
Machine A doesnt know how to route packets to Machine B. Reboot
everything, router first, see if it goes away. Otherwise, now is the
time to learn to debug routing problems. traceroute is the best starting
place
