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

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.10.0, 0.9.6
• Fix Version/s: 0.9.6
• Component/s: storm-core
• Assignee: Kyle Nusbaum
• Reporter: Derek Dagit
• Created: 17/Aug/15 21:44
• Updated: 17/Oct/15 14:20
• Resolved: 05/Sep/15 01:59

Description

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.

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