[ https://issues.apache.org/jira/browse/STORM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425554#comment-16425554 ]
Ethan Li edited comment on STORM-2983 at 4/4/18 3:39 PM: --------------------------------------------------------- I think [~kabhwan] has a very good point. So I am proposing: 1) a new Jira for RAS issues. We all agree that RAS issues are important and need to be addressed. I believe it's better to have a separate Jira to discuss and fix them in the right way. 2) checking whether outgoing stream/tasks/connections exists in the worker instead of checking topology.worker. I agree that this is the right way to do it and it's more flexible. It also keeps this minor optimization. (Made updates to the PR). was (Author: ethanli): I think [~kabhwan] has a very good point. So I am proposing: 1) a new Jira for RAS issues. We all agree that RAS issues are important and need to be addressed. I believe it's better to have a separate Jira to discuss and fix them in the right way. 2) checking whether outgoing stream/tasks/connections exists in the worker instead of checking topology.worker. I agree that this is the right way to do it and it's more flexible. It also keeps this minor optimization. > Some topologies not working properly > ------------------------------------- > > Key: STORM-2983 > URL: https://issues.apache.org/jira/browse/STORM-2983 > Project: Apache Storm > Issue Type: Bug > Reporter: Ethan Li > Assignee: Ethan Li > Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > For example, > {code:java} > bin/storm jar storm-loadgen-*.jar > org.apache.storm.loadgen.ThroughputVsLatency --spouts 1 --splitters 2 > --counters 1 -c topology.debug=true > {code} > 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)