Github user srdo commented on the pull request:
https://github.com/apache/storm/pull/1209#issuecomment-199321366
The hang checks should now support writing errors to Zookeeper, extending
the timeout by interacting with an OutputCollector, setting different time
limits per component, and disabling the checks entirely by setting the
timelimit/check frequency to null. I took a quick look at the metrics system,
but can't really see a nice way of logging to it if we're potentially shutting
down the worker when this system is triggered.
I'm not sure the automatic/manual hang timeout resets are really necessary
on SpoutOutputCollector, since I don't see a case where a user would want to
hang in nextTuple while still emitting tuples. Let me know if they should be
removed.
I think this PR is ready for re-review.
---
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.
---
