Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/772#issuecomment-145159356
why would tuples start to timeout given before the tuple timeout occurs we
have a tick tuple that fires and tries to flush the batch even if it has not
reached the desired size? I thought the only difference the users would see now
is that their latency may go up in a low throughput system unless they
explicitly set the batch size = 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.
---
