Github user nathanmarz commented on the pull request:
https://github.com/apache/storm/pull/339#issuecomment-67589509
Yea, most of this can be addressed by allocating more resources so Kafka
has enough retention to not truncate the data before the topology can be fixed.
+1
---
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.
---
