[
https://issues.apache.org/jira/browse/STORM-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058204#comment-15058204
]
ASF GitHub Bot commented on STORM-1377:
---------------------------------------
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.
> nimbus_auth_test: very short timeouts causing spurious failures
> ---------------------------------------------------------------
>
> Key: STORM-1377
> URL: https://issues.apache.org/jira/browse/STORM-1377
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 0.10.0, 0.11.0
> Reporter: Derek Dagit
> Assignee: Derek Dagit
> Priority: Minor
>
> This is caused by a units mismatch. We are waiting 30 ms for the thrift
> server to reply when we thought we were waiting 30s. This means that
> sometimes when we expect NotAliveException, we instead get
> TTransportException(SocketTimeoutException), and this fails the assertions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
