Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/625#issuecomment-120818894
@errordaiwa with 2.10.4 you may try the single argument waitFor(long
sequeuce) in DisruptrorQueue.java and observe the CPU usage with a high bolt
count like what you mentioned in the issue. Also see if the bolts are receiving
the tuples without a delay.
---
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.
---
