[jira] [Comment Edited] (STORM-2983) Some topologies not working properly

["Ethan Li (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STORM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424644#comment-16424644 ] 

Ethan Li edited comment on STORM-2983 at 4/3/18 9:36 PM:
---------------------------------------------------------

As stated before, we definitely need to read through the code and see what RAS breaks and fix them. That's why I suggested to file a separate Jira to track it and have somebody to do it.  I want to get this in because it blocks my current work for quite a long time and I want to get that done sooner than later, if this is OK with you.


was (Author: ethanli):
As state before, we definitely need to read through the code and see what RAS breaks and fix them. That's why I suggested to file a separate Jira to track it and have somebody to do it.  I want to get this in because it blocks my current work for quite a long time and I want to get that done sooner than later, if this is OK with you.

> 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)