Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/268#issuecomment-59487520
Support we are sending data from worker A to worker B, to solve
STORM-404(Worker on one machine crashes due to a failure of another worker on
another machine),
I think we can adopt the following logics:
case1: when B is down:
1. B is lost, but A is still belive B is alive.
2. A try to send data to B, and then it triggers reconnect
3. The Nimbus find B is lost, and notify A.
4. A got notification that B is down, it will need to interrupt the
reconnection of step 2( by closing the connection)
5. The reconnection of step 2 is interuppted, it exit. it will not throw
RuntimeException.
The key change is at step 4. A need to interrupt the reconnection to an
obsolete worker.
case 2: when B is alive, but the connection from A to B is down
1. A trigger reconnection logic
2. reconnection timeout
3. A cannot handle this failure, A throws RuntimeException.
---
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.
---
