[
https://issues.apache.org/jira/browse/STORM-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605992#comment-14605992
]
Brian Fleming commented on STORM-908:
-------------------------------------
Clarification, this is on amazon EC2 instances, and it seems to be host the
hostname is resolved when using the public DNS alias. EC2 instances have two
IPs, an external and an internal one. I'd like to know how the IP address is
resolved in the code.
I've seen a handful of posts reporting this same problem with Storm on AWS, but
no resolution.
> AWS workers can't communicate due to Netty-Client hostname resolution
> ---------------------------------------------------------------------
>
> Key: STORM-908
> URL: https://issues.apache.org/jira/browse/STORM-908
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.9.4
> Reporter: Brian Fleming
> Priority: Minor
>
> Observed that there is some kind of problem blocking communication between
> workers. I think manually editing the /etc/hosts file is a workaround.
> ubuntu@ip-10-9-255-123
> /home/ubuntu/apache-storm-0.9.4/logs/worker-6714.log
> 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-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-west-2.compute.internal/10.9.255.20:6711
> failed: java.lang.RuntimeException: Returned channel was actually not
> established
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
