[STORM-2983] Some topologies not working properly

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Labels: pull-request-available
• Epic Link: Release Apache Storm 2.0.0
• Assignee: Ethan Li
• Reporter: Ethan Li
• Created: 28/Feb/18 14:46
• Updated: 09/Apr/18 14:33
• Resolved: 05/Apr/18 13:12

Description

For example,

bin/storm jar storm-loadgen-*.jar org.apache.storm.loadgen.ThroughputVsLatency --spouts 1 --splitters 2 --counters 1 -c topology.debug=true

on ResourceAwareScheduler not working properly.

With default cluster settings, there will be only one __acker-executor and it will be on a separate worker. And it looks like the __acker-executor was not able to receive messages from spouts and bolts. And spouts and bolts continued to retry sending messages to acker. It then led to another problem:
STORM-2970

I tried to run on storm right before https://github.com/apache/storm/pull/2502 and right after and confirmed that this bug should be related to it

Issue Links

• causes: STORM-2970 JCQueue can be full and will throw IllegalStateException
• is related to: STORM-3021 RAS doesn't honor Config.TOPOLOGY_WORKERS
• links to: GitHub Pull Request #2614