You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/09/30 03:14:04 UTC

[jira] [Updated] (STORM-908) AWS workers can't communicate due to Netty-Client hostname resolution

     [ https://issues.apache.org/jira/browse/STORM-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-908:
-------------------------------
    Component/s: storm-core

> 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
>          Components: storm-core
>    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)