Re: AWS Hostnames not resolving properly Netty-Client-ip-10

[Dillian Murphey <cr...@gmail.com>]

I went with all local IP addresses, and that seems to work. I was use the
public DNS alias ec2-54-x-y-z.  I changed it to the local addresses
10.x.y.z.  I typically use the public DNS alias like ec2-54-x-y-z because
that gets resolved to local addresses if they can, which is kind of nice,
but guess in this case I'll go with just local addressess to avoid this
problem.

On Wed, Jun 24, 2015 at 9:42 AM, Dillian Murphey <cr...@gmail.com>
wrote:

> I'm seeing this reported elsewhere but finding no replies.
>
> Does anyone know what the problem is here with host hostnames are resolved
> by Storm when running on AWS?
>
> Clearly that is not a hostname, prefixed with Netty-Client.
>
> 2015-06-24T07:13:07.856+0000 b.s.m.n.Client [INFO] connection attempt 24
> to Netty-Client-ip-10-9-255-20.us <http://netty-client-ip-10-9-255-20.us/>
> -west-2.compute.internal/10.9.255.20:6711 scheduled to run in 387 ms
>
> 2015-06-24T07:13:08.244+0000 b.s.m.n.Client [ERROR] connection attempt 24
> to Netty-Client-ip-10-9-255-20.us <http://netty-client-ip-10-9-255-20.us/>
> -west-2.compute.internal/10.9.255.20:6711 failed:
> java.lang.RuntimeException: Returned channel was actually not established
>
>
>
> I think a work-around is to manually edit the /etc/hosts file. I had a
> different issue I believe preventing me from fully testing that.
>
>
>
>