Hi.
2009/4/24 Raghu Angadi
>
> Telnet failure to localhost is expected and is unrelated since servers are
> not listening on it.
>
> What is the ip address of this machine?
>
> Try 'telnet different_datanode_ip 50010' _from_ this machine. What do you
> see?
>
> Raghu.
>
All seems to be solved,
Telnet failure to localhost is expected and is unrelated since servers
are not listening on it.
What is the ip address of this machine?
Try 'telnet different_datanode_ip 50010' _from_ this machine. What do
you see?
Raghu.
Stas Oskin wrote:
Hi.
Shouldn't you be testing connecting _from_
Just to clarify one point - the iptables were running on 2nd DataNode which
I didn't check, as I was sure the problem is in the NameNode/DataNode, and
on NameNode/DataNode. But I can't understand what and when launched them,
as I checked multiple times and nothing was running before. Moreover, the
Hi.
> Also iptables -L for each machine as an afterthought - just for paranoia's
> sake
>
Well, I started preparing all the information you requested, but when I got
to this stage - I found out there were INDEED iptables running on 2 servers
from 3.
The strangest thing is that I don't recall en
Can you give us your network topology ?
I see that at least 3 ip addresses
192.168.253.20, 192.168.253.32 and 192.168.253.21
In particular the fs.default.name which you have provided, the
hadoop-site.xml for each machine,
the slaves file, with ip address mappings if needed and a netstat -a -n -t
-
Hi.
Maybe, but there will still be at least one virtual network adapter on the
> host. Try turning them off.
Nope, still throws "No route to host" exceptions.
I have another IP address defined on this machine - 192.168.253.21, for the
same network adapter.
Any idea if it has impact?
>
>
>> T
Stas Oskin wrote:
Hi.
2009/4/23 Matt Massie
Just for clarity: are you using any type of virtualization (e.g. vmware,
xen) or just running the DataNode java process on the same machine?
What is "fs.default.name" set to in your hadoop-site.xml?
This machine has OpenVZ installed indeed, bu
Hi.
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.
>
Same static IP's for all servers.
By the way, I have the fs.default.name defined in IP address could it be
somehow related?
I read that there were
Hi.
Shouldn't you be testing connecting _from_ the datanode? The error you
> posted is while this DN is trying connect to another DN.
You might be into something here indeed:
1) Telnet to 192.168.253.20 8020 / 192.168.253.20 50010 works
2) Telnet to localhost 8020 / localhost 50010 doesn't wor
Hi.
2009/4/23 Matt Massie
> Just for clarity: are you using any type of virtualization (e.g. vmware,
> xen) or just running the DataNode java process on the same machine?
>
> What is "fs.default.name" set to in your hadoop-site.xml?
>
This machine has OpenVZ installed indeed, but all the appl
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 addr
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 inter
I wonder if this is an obscure case of out of file descriptors. I would
expect a different message out of the jvm core
On Wed, Apr 22, 2009 at 5:34 PM, Matt Massie wrote:
> Just for clarity: are you using any type of virtualization (e.g. vmware,
> xen) or just running the DataNode java process o
Just for clarity: are you using any type of virtualization (e.g. vmware,
xen) or just running the DataNode java process on the same machine?
What is "fs.default.name" set to in your hadoop-site.xml?
-Matt
On Wed, Apr 22, 2009 at 5:22 PM, Stas Oskin wrote:
> Hi.
>
> Is it possible to paste the
Hi.
Is it possible to paste the output from the following command on both your
> DataNode and NameNode?
>
> % route -v -n
>
Sure, here it is:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.253.0 0.0.0.0 255.255.255.0 U
Stas-
Is it possible to paste the output from the following command on both your
DataNode and NameNode?
% route -v -n
-Matt
On Wed, Apr 22, 2009 at 4:36 PM, Stas Oskin wrote:
> Hi.
>
> The way to diagnose this explicitly is:
> > 1) on the server machine that should be accepting connections o
Hi.
The way to diagnose this explicitly is:
> 1) on the server machine that should be accepting connections on the port,
> telnet localhost PORT, and telnet IP PORT you should get a connection, if
> not then the server is not binding the port.
> 2) on the remote machine verify that you can communi
Hi.
There is some mismatch here.. what is the expected ip address of this
> machine (or does it have multiple interfaces and properly routed)? Looking
> at the "Receiving Block" message DN thinks its address is 192.168.253.20 but
> NN thinks it is 253.32 (and client is able to connect using 253.3
There is some mismatch here.. what is the expected ip address of this
machine (or does it have multiple interfaces and properly routed)?
Looking at the "Receiving Block" message DN thinks its address is
192.168.253.20 but NN thinks it is 253.32 (and client is able to connect
using 253.32).
the no route to host message means one of two things, either there is no
actual route, which would have generated a different error, or some firewall
is sending back a new route message.
I have seen the now route to host problem several times, and it is usually
because there is a firewall in place
Hi.
"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
I used
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 t
Hi.
2009/4/22 jason hadoop
> Most likely that machine is affected by some firewall somewhere that
> prevents traffic on port 50075. The no route to host is a strong indicator,
> particularly if the Datanote registered with the namenode.
>
Yes, this was my first thought as well. But there is n
Most likely that machine is affected by some firewall somewhere that
prevents traffic on port 50075. The no route to host is a strong indicator,
particularly if the Datanote registered with the namenode.
On Tue, Apr 21, 2009 at 4:18 PM, Philip Zeyliger wrote:
> Very naively looking at the code, t
Very naively looking at the code, the exception you see is happening in the
write path, on the way to sending a copy of your data to a second data
node. One data node is pipelining the data to another, and that connection
is failing. The fact that "DatanodeRegistration" is mentioned in the
except
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 hos
26 matches
Mail list logo
