Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of stas.oskin@gmail.com
 designates 209.85.220.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=PyzqNspB7g880cByqcZRDEvBbiBezlj1kd/nhBsnW+MiA6rpvJaVGdlxZ8uIdnHspV
         ZLdgfRchxQ6ysYVgbeEpgIN6mjUfuioA7cwnRVxWfyPuxkRBMifcS72ViFmUBXGX0FPg
         GTvEAhi7AJPUvbortr/DrhLZ6JLiRdgjIPIlE=
MIME-Version: 1.0
In-Reply-To: <49EF635C.2040902@yahoo-inc.com>
References: <77938bc20904211221i29a98827k270c4ac7dd7eea36@mail.gmail.com>
	 <77938bc20904211354j48936e62ue083a41e50ebedb1@mail.gmail.com>
	 <15da8a100904211618m24ba4906mac1031b6e66586ad@mail.gmail.com>
	 <314098690904211950h64b82deal1fd1b279a36b871c@mail.gmail.com>
	 <77938bc20904220220q1fbef7dex1b1e1d18275b6c21@mail.gmail.com>
	 <49EF635C.2040902@yahoo-inc.com>
Date: Thu, 23 Apr 2009 02:11:14 +0300
Message-ID: <77938bc20904221611y60b2ed88kce36980ed0069691@mail.gmail.com>
Subject: Re: No route to host prevents from storing files to HDFS
From: Stas Oskin <stas.oskin@gmail.com>
To: core-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001636c5bb1349dc0904682ce189

--001636c5bb1349dc0904682ce189
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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.32).
>
> If you want to find the destination ip that this DN is unable to connect
> to, you can check client's log for this block number.
>


Hmm, .253.32 is the client workstation (has only our test application with
core-hadoop.jar + configs).

The expected address of the DataNode should be 192.168.253.20.

According to what I seen, the problem is in DataNode itself - it just throws
the Datanoderegistration every so often:


2009-04-23 00:05:05,961 INFO org.apache.hadoop.dfs.DataNode: Receiving block
blk_7209884038924026671_8033 src: /192.168.253.32:42932
 dest: /192.168.253.32:50010
2009-04-23 00:05:05,962 INFO org.apache.hadoop.dfs.DataNode: writeBlock
blk_7209884038924026671_8033 received exception java.net.NoR
outeToHostException: No route to host
2009-04-23 00:05:05,962 ERROR org.apache.hadoop.dfs.DataNode:
DatanodeRegistration(192.168.253.20:50010, storageID=DS-1790181121-127
.0.0.1-50010-1239123237447, infoPort=50075, ipcPort=50020):DataXceiver:
java.net.NoRouteToHostException: No route to host
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:574)
        at
org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
        at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:402)
        at
org.apache.hadoop.dfs.DataNode$DataXceiver.writeBlock(DataNode.java:1255)
        at
org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:1092)
        at java.lang.Thread.run(Thread.java:619)

Regards.

--001636c5bb1349dc0904682ce189--