Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/941#issuecomment-164796992
> Hi @d2r , could you change 3 secs a little longer? We've met the case in
production that for a large topology(say, 800+ workers, 4000+ tasks), this may
timeout.
@unsleepy22, these are timeouts for simple tests. Normally much, much
shorter timeouts work. It's just that on single-core environments, like that
of our travis-ci, some of the clients cannot quite reply in 30 milliseconds.
This should not affect any deployment in production; it is merely for running
tests.
---
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.
---
