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/10/09 03:27:27 UTC

[jira] [Updated] (STORM-556) netty Client reconnect bug

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

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

> netty Client  reconnect bug
> ---------------------------
>
>                 Key: STORM-556
>                 URL: https://issues.apache.org/jira/browse/STORM-556
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 0.9.2-incubating
>            Reporter: Xavier Fu
>            Assignee: Xavier Fu
>              Labels: ClientID, hangup, netty
>             Fix For: 0.9.3
>
>
> if a storm worker die then restarted and the nimbus  reassign the task on the restarted worker with same host:port, the upstream task will not reconnect the host:port and the topology will hang up。
> because the connect has broken and netty Client flush timer 
> if (null != channel && channel.isWritable()) {
>                             flush(channel);
> }
> always false.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)