Github user dossett commented on the pull request:
https://github.com/apache/storm/pull/664#issuecomment-131648086
@arunmahadevan Thank you for the feedback! I have added a tick tuple
feature to address your first point (I am already using this locally, I forgot
to include it in this PR).
You are right that I attempt to sync even when the write fails. I agree
that this is unlikely to succeed, but it seems worthwhile to try to "save" as
many tuples as possible.
With this tick tuple change I think the code is very close to your
recommendation. If the bolt is in a bad state the tick tuples will
periodically try to rotate the file and all errors will be reported up through
```this.collector.reportError(e)```
---
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.
---
