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
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
