[
https://issues.apache.org/jira/browse/STORM-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701818#comment-14701818
]
Derek Dagit commented on STORM-996:
-----------------------------------
Suspecting maybe the [asynchronous
write|https://github.com/apache/storm/blob/3b1b3bfa595851afd468594079caa7c772dafd48/storm-core/src/jvm/backtype/storm/messaging/netty/Client.java#L323]
in Client#flushMesages might be the issue. We create a future here to write
the data asynchronously, but the new thread does not have to be scheduled to
run before subsequent batches are written, and so batches can be send in the
wrong order.
> 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)
