Hi, a vpn or simply first uploading the files to an ec2 node is the best option
but an alternative is to use the external interface/IP instead of the
internal in the hadoop config¸ I assume this will be slower and more
On Fri, Aug 24, 2012 at 4:54 AM, igor Finkelshteyn <[EMAIL PROTECTED]> wrote:
> I've seen a bunch of people with this exact same question all over Google with no answers. I know people have successful non-temporary clusters in EC2. Is there really no one that's needed to deal with having EC2 expose external addresses instead of internal addresses before? This seems like it should be a common thing.
> On Aug 23, 2012, at 12:34 PM, igor Finkelshteyn wrote:
>> 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=/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?
Håvard Wahl Kongsgård
Faculty of Medicine &
Department of Mathematical Sciences