Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/795#issuecomment-148222144
@kishorvpatil
Yeah, after this PR gets merged. :)
Thinking it once more, since default nimbus.task.timeout.secs is 30,
retrying for each 1 secs seems not be short.
Just curious about adjusting max_wait_ms may affect HashedWheelTimer's CPU
usage as you stated.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
