[ 
https://issues.apache.org/jira/browse/STORM-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15373044#comment-15373044
 ] 

Kevin Conaway commented on STORM-1609:
--------------------------------------

Thanks [~kabhwan].

That said, this backport is fairly non-invasive and does fix a very nasty issue 
which causes the topology to hang.  If fixes are still being made to 0.10.x, 
I'd like to see this one go in for those folks who are unwilling or unable to 
upgrade to 1.0.x

> Netty Client is not best effort delivery on failed Connection
> -------------------------------------------------------------
>
>                 Key: STORM-1609
>                 URL: https://issues.apache.org/jira/browse/STORM-1609
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Sanket Reddy
>            Assignee: Sanket Reddy
>
> f Worker-A has connection to Worker-B that is unused ( and if Worker-B 
> restarted), we drop messages because Channel is not in good state. Can we 
> avoid message drop until we succeed in making new connection or a timeout?



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

Reply via email to