GitHub user miguno opened a pull request:
https://github.com/apache/storm/pull/429
STORM-329: fix cascading Storm failure by improving reconnection strategy
and buffering messages
**This PR contains the same code as
https://github.com/apache/storm/pull/428 but as a single commit for a cleaner
commit history of our Storm repo.**
--
This is an improved version of the original pull request discussed at
https://github.com/apache/storm/pull/268. Please refer to the discussion in
the link above.
**Note**: Please give attribution to @tedxia when merging the pull request
as he did a lot (most?) of the work in this pull request.
The changes of this pull request include:
- Most importantly, we fix a bug in Storm that may cause a cascading
failure in a Storm cluster, to the point where the whole cluster becomes
unusable. This is achieved by the work described in the next bullet points.
- We refactor and improve the Netty messaging backend, notably the client.
- During the initial startup of a topology, Storm will now wait until
worker (Netty) connections are ready for operation. See the [original
discussion thread](https://github.com/apache/storm/pull/268) for the detailed
explanation and justification of this change.
@clockfly, @tedxia: Please add any further comments to STORM-329 to this
pull request, if possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/miguno/storm 0.10.0-SNAPSHOT-STORM-329-diff
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/429.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 #429
----
commit 205eaf4ebe28ab5550a842ea9aabd23b41678743
Author: Michael G. Noll <mn...@verisign.com>
Date: 2015-02-11T18:55:53Z
STORM-329: fix cascading Storm failure by improving reconnection strategy
and buffering messages
Thanks to @tedxia for the initial work on this patch, which covered a
lot if not most of the work!
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
