[STORM-3309] TickTupleTest is still flaky

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: storm-server
• Labels: pull-request-available
• Assignee: Stig Rohde Døssing
• Reporter: Stig Rohde Døssing
• Created: 04/Jan/19 22:59
• Updated: 16/Mar/19 03:26
• Resolved: 30/Jan/19 11:42

Description

testTickTupleWorksWithSystemBolt Time elapsed: 6.802 s <<< FAILURE!
java.lang.AssertionError: Iteration 1 expected:<52000> but was:<51000>

The test runs a topology in a local cluster with time simulation. One of the bolts has tick tuples enabled, and the test tries to check that the ticks arrive with 1 second intervals.

As far as I can tell, the problem is that time simulation doesn't cover the bolt and spout executors. When the test increases simulated time by 1 second and waits for the cluster to idle, the test expects that to mean that the bolt will at that point have consumed the tick. In some cases this doesn't happen, and multiple tick tuples may end up queued before the bolt consumes them. Since the bolt is responsible for generating the timestamp, the test will fail.

Issue Links

• links to: GitHub Pull Request #2933