Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of iefinkel@gmail.com designates
 209.85.160.48 as permitted sender)
From: igor Finkelshteyn <iefinkel@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_84870A6F-D763-4C5B-81D9-07E8C73BF1C0"
Subject: Re: Hadoop on EC2 Managing Internal/External IPs
Date: Thu, 23 Aug 2012 20:09:32 -0700
In-Reply-To: 
 <CA+R1ZMMBK20+wm8eJPgYZgrLfdyPqYM=3DrUEuXhsjCnaLr7gA@mail.gmail.com>
To: user@hadoop.apache.org
References: <AE5E3718-09A0-4B4C-8C4E-AC64220CF30C@gmail.com>
 <CA+R1ZMMBK20+wm8eJPgYZgrLfdyPqYM=3DrUEuXhsjCnaLr7gA@mail.gmail.com>
Message-Id: <D9B20CCC-F10D-48D1-A50D-F2A1FE67078C@gmail.com>


--Apple-Mail=_84870A6F-D763-4C5B-81D9-07E8C73BF1C0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

That would work, but wouldn't a much simpler solution just be to force =
the machines in the cluster to always pass around their external FQDNs, =
since those will properly resolve to the internal or external IP =
depending on what machine is asking? Is there no way to just do that?


On Aug 23, 2012, at 8:02 PM, Aaron Eng wrote:

> Hi Igor,
>=20
> Amazon offers a service where you can have a VPN gateway on your =
network that leads directly back to the network where youre instances =
are at.  So that 10.123.x.x subnet would be connected off of the VPN =
gateway on your network and you'd set up your routers/routing to push =
traffic for that subnet at the gateway. =20
>=20
> On Thu, Aug 23, 2012 at 12:34 PM, igor Finkelshteyn =
<iefinkel@gmail.com> wrote:
> 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:
>=20
> 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]
>=20
> 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?
>=20
> Eli
>=20


--Apple-Mail=_84870A6F-D763-4C5B-81D9-07E8C73BF1C0
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>That would work, but wouldn't a much simpler solution just be to force the machines in the cluster to always pass around their external FQDNs, since those will properly resolve to the internal or external IP depending on what machine is asking? Is there no way to just do that?</div><div><br></div><br><div><div>On Aug 23, 2012, at 8:02 PM, Aaron Eng wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Igor,<div><br></div><div>Amazon offers a service where you can have a VPN gateway on your network that leads directly back to the network where youre instances are at. &nbsp;So that 10.123.x.x subnet would be connected off of the VPN gateway on your network and you'd set up your routers/routing to push traffic for that subnet at the gateway. &nbsp;<br>
<br><div class="gmail_quote">On Thu, Aug 23, 2012 at 12:34 PM, igor Finkelshteyn <span dir="ltr">&lt;<a href="mailto:iefinkel@gmail.com" target="_blank">iefinkel@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
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:<br>

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

<br>
Eli</blockquote></div><br></div>
</blockquote></div><br></body></html>
--Apple-Mail=_84870A6F-D763-4C5B-81D9-07E8C73BF1C0--