[
https://issues.apache.org/jira/browse/STORM-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285869#comment-15285869
]
ASF GitHub Bot commented on STORM-1837:
---------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/1417#issuecomment-219600127
@kishorvpatil
Nice finding. I think it should reflect STORM_TEST_TIMEOUT_MS, but it can
be done with another JIRA issue since it seems not related on this PR.
Btw, other test failure is observed from Travis CI, which I think is also
not related to this PR.
```
Running org.apache.storm.utils.DisruptorQueueTest
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.352 sec
<<< FAILURE! - in org.apache.storm.utils.DisruptorQueueTest
testInOrderBatch(org.apache.storm.utils.DisruptorQueueTest) Time elapsed:
0.405 sec <<< FAILURE!
junit.framework.AssertionFailedError: producer 0 is still alive
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertFalse(Assert.java:39)
at junit.framework.TestCase.assertFalse(TestCase.java:210)
at
org.apache.storm.utils.DisruptorQueueTest.run(DisruptorQueueTest.java:135)
at
org.apache.storm.utils.DisruptorQueueTest.testInOrderBatch(DisruptorQueueTest.java:106)
```
@srdo
I guess what @kishorvpatil reported is a kind of intermittent failure,
since one of storm-core build is passed on Travis CI.
> Running local clusters without simulating time breaks
> Testing.completeTopology, and may cause message loss
> ----------------------------------------------------------------------------------------------------------
>
> Key: STORM-1837
> URL: https://issues.apache.org/jira/browse/STORM-1837
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 1.0.0, 2.0.0, 1.0.1
> Reporter: Stig Rohde Døssing
> Priority: Minor
>
> Since https://github.com/apache/storm/pull/810 it is no longer possible to
> call Testing.completeTopology when time is not simulating, because a call to
> advance-cluster-time is made from the function, which calls Time/advanceTime.
> advance-cluster-time should only be called if time is simulating.
> Since https://github.com/apache/storm/pull/830 a local cluster run without
> time simulation may lose messages. When a worker emits messages for a worker
> that hasn't started yet, the message is lost. This can happen because spouts
> may start emitting before all workers have started, when time simulation is
> disabled. Local clusters usually run without message timeouts, so this will
> make tests relying on Testing.withLocalCluster flaky.
> The problem is that there are no longer any queues to store messages for
> workers that haven't started yet. See
> https://github.com/apache/storm/pull/830/files#diff-c6ff4208ef84c7a5a1a6b8b6bd1f7d19R104.
> A queue should be added for messages for workers that haven't registered a
> receive callback yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
