[
https://issues.apache.org/jira/browse/STORM-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185532#comment-15185532
]
ASF GitHub Bot commented on STORM-1609:
---------------------------------------
GitHub user redsanket opened a pull request:
https://github.com/apache/storm/pull/1194
[STORM-1609] Netty Client is not best effort delivery on failed Connection
If 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?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/redsanket/storm netty-best-effort
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/1194.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1194
----
commit 54b6ac4975582bb6b3ef3511369e52ad81db05b3
Author: Sanket <schintap@untilservice-lm>
Date: 2016-03-08T19:06:39Z
netty loss of messages resolution
----
> 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)
