Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/893#issuecomment-165185880
@harshach with 15 secs, the throughput was very low since the spout could
not emit more tuples after hitting max.spout.pending. The low value (1s)
default also makes sure that the value is not more than
topology.message.timeout.secs in case user changes the default timeout (if the
value is more it would cause unnecessary duplicates). There seems to be no way
to get the message timeout value in getComponentConfiguration and adjust the
tick tuple interval accordingly.
The 1s is only the default, the user can change it via HiveOptions if
compaction is a concern.
---
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.
---
