[jira] [Resolved] (STORM-996) netty-unit-tests/test-batch demonstrates out-of-order delivery

["Jungtaek Lim (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim resolved STORM-996.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.0

Nice work, [~knusbaum]
I merged into master and 0.10.x-branch.

> 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: Kyle Nusbaum
>            Priority: Blocker
>             Fix For: 0.10.0
>
>         Attachments: storm-996-OrderedDownstreamThreadPoolExecutor-failed.txt.bz2
>
>
> 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)