Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/521#issuecomment-98942013
@d2r Thanks for comment, I can wait it. :)
Btw, your branch doesn't follow Nathan's comment.
```
In short, the code in the write-lock is fine â it's the code in the read
lock that needs to be fixed. As part of that, the code looking up the node+port
for a task needs to be moved back to this function and not happen before the
tuple goes on the transfer queue.
```
Root reason is from mk-transfer-fn.
It matches task and node+port but there's some latencies from adding
Transfer queue to sending via Netty. Task to node+port can be changed during
latency so we should delegate matching it to very close to sending, within read
lock to get safely.
So I'd like you to compare mine and yours when you come back. Thanks!
---
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.
---
