Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of iefinkel@gmail.com designates
 209.85.160.48 as permitted sender)
From: igor Finkelshteyn <iefinkel@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Hadoop on EC2 Managing Internal/External IPs
Date: Thu, 23 Aug 2012 12:34:44 -0700
Message-Id: <AE5E3718-09A0-4B4C-8C4E-AC64220CF30C@gmail.com>
To: user@hadoop.apache.org
Mime-Version: 1.0 (Apple Message framework v1280)

Hi,
I'm currently setting up a Hadoop cluster on EC2, and everything works =
just fine when accessing the cluster from inside EC2, but as soon as I =
try to do something like upload a file from an external client, I get =
timeout errors like:

12/08/23 12:06:16 ERROR hdfs.DFSClient: Failed to close file =
/user/some_file._COPYING_
java.net.SocketTimeoutException: 65000 millis timeout while waiting for =
channel to be ready for connect. ch : =
java.nio.channels.SocketChannel[connection-pending =
remote=3D/10.123.x.x:50010]

What's clearly happening is my NameNode is resolving my DataNode's IPs =
to their internal EC2 values instead of their external values, and then =
sending along the internal IP to my external client, which is obviously =
unable to reach those. I'm thinking this must be a common problem. How =
do other people deal with it? Is there a way to just force my name node =
to send along my DataNode's hostname instead of IP, so that the hostname =
can be resolved properly from whatever box will be sending files?

Eli=