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.
