Github user nathanmarz commented on the pull request:
https://github.com/apache/storm/pull/349#issuecomment-87742572
Without the r/w lock the following can happen:
1. Sender S grabs a socket to worker A for task B
2. Refresh connections learns task B is now on worker C, changes the
connection, and closes the old socket
3. Sender S tries to send data on a closed socket
An atom does not protect against this.
---
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.
---
