[
https://issues.apache.org/jira/browse/STORM-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14721639#comment-14721639
]
Derek Dagit commented on STORM-996:
-----------------------------------
Following up briefly: I wanted to see if the nature of the failures when using
the OrderedDownstreamThreadPoolExecutor was different from before, but with
another test run just now it appears the same.
In the quoted example, it shows individual messages—but not batches—being
delivered out of order from the perspective of the test. I ran it again just
now, and the test failed with long sequences of messages being delivered
out-of-order as in the description. I will attach a file with just the test
failure output as an example.
> netty-unit-tests/test-batch demonstrates out-of-order delivery
> --------------------------------------------------------------
>
> Key: STORM-996
> URL: https://issues.apache.org/jira/browse/STORM-996
> Project: Apache Storm
> Issue Type: Bug
> Affects Versions: 0.10.0
> Reporter: Derek Dagit
> Assignee: Derek Dagit
> Priority: Blocker
>
> backtype.storm.messaging.netty-unit-test/test-batch
> One example of output. Similar things happen sporadically and vary widely by
> number of failed assertions.
> Tuples are not just skewed, but actually seem to come in out-of-order.
> {quote}
> actual: (not (= "66040" "66041"))
> at: test_runner.clj:105
> expected: (= req_msg resp_msg)
> actual: (not (= "66041" "66042"))
> at: test_runner.clj:105
> expected: (= req_msg resp_msg)
> actual: (not (= "66042" "66040"))
> at: test_runner.clj:105
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
