Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/339#issuecomment-67582859
@nathanmarz the re-emit can hit this issue in many pathological cases , bad
kafka config, transient network failure causing storm batches to fail
repeatedly while kafka queue with low retention getting truncated, very slow
topology with really fast kafka producers with low retention rate so mostly
around kafka config with lower retention rates.
I have made the change you suggested during reemit we don't catch exception
but let the spout fail.
---
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.
---
