Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/268#issuecomment-60863620
Hi Ted,
```
This will still cause another worker crash.
Now there are two things happen in parallel, first nimbus inform worker A
that worker B is not alive by zk timeout, second worker A connect to worker B
by netty. When worker B died for some reason, we can't guarantee which happen
first, if the connection from worker A to worker B broken first, then client's
status will became closing, but right now nimbus has't inform worker A that
worker has died, then worker A will still send message to worker B, the
Exception will throw and what STORM-404 describe will happen.
```
Suppose worker A send msg to worker B.
If B dies, At A, it will have multiple reconnection try. A will get
notified that B is dead, and will set closing flag of Client(to B), which will
abort the reconnection process, no RuntimeException will be thrown.
If there is a network partitioning issue, suppose worker A is isolated from
the rest of the cluster. A will not get notified that B is not alive. Then A
will continue to retry reconnection to B for multiple times, and throw
RuntimeException, and exit eventually. In this case, A cannot recover, throw is
best option.
---
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.
---
