Github user rsltrifork commented on the pull request:
https://github.com/apache/storm/pull/700#issuecomment-144703338
Does this solve the problem of tuple timeout, when a bolt is completely
stalled waiting for an external component to get back up?
I believe waiting for too long in a bolt triggers the tuple timeout, which
causes the Spout to reemit, which is usually not what we want, when a bolt is
waiting in a controlled manner before it can resume computation.
Ideally, the tuple timeout should be used as a last resort to detect that
internal storm components don't respond. And back pressure should ensure that
the Spout doesn't reemit to temporarily busy/blocked bolts - regardless of
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.
---
