Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/268#issuecomment-61373371
I traced back the bug of message loss.
I found this issue is introduced by storm-350.
(https://github.com/apache/storm/pull/134/files#diff-4cbcb6fa47274d6cf66d70585f98cbefR202)
After upgrading from disruptor 2.10.1 to 3.2.1
---
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.
---
