You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Kevin Conaway (JIRA)" <ji...@apache.org> on 2016/07/12 13:25:20 UTC
[jira] [Commented] (STORM-1609) Netty Client is not best effort
delivery on failed Connection
[ https://issues.apache.org/jira/browse/STORM-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372869#comment-15372869 ]
Kevin Conaway commented on STORM-1609:
--------------------------------------
[~ptgoetz] can this be backported to 0.10.2? We're seeing this (and STORM-1394) fairly frequently in Storm 0.10.0. I backported this to a custom branch and it fixes the issue for us.
We're unable to upgrade to Storm 1.0 due to STORM-1879
> 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)