Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/625#issuecomment-120260564
After digging further I suspect the volatile `numWaiters` @
https://github.com/LMAX-Exchange/disruptor/blob/2.10.1/code/src/main/com/lmax/disruptor/BlockingWaitStrategy.java
could be the culprit. If a volatile is updated by multiple threads we could
be losing updates which would manifest as consumers not being waken up when
there is an item in the queue.
@errordaiwa lmax-disruptor 2.10.4 appear to have a fix for this issue. Can
you try with this version and call the waitFor without any timeout ?
---
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.
---
