[jira] [Updated] (STORM-2983) Some topologies not working properly
[
https://issues.apache.org/jira/browse/STORM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-2983:
Priority: Critical (was: Major)
> 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: Critical
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Time Spent: 0.5h
> 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)
[jira] [Updated] (STORM-2983) Some topologies not working properly
[
https://issues.apache.org/jira/browse/STORM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated STORM-2983:
--
Labels: pull-request-available (was: )
> 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
>
> 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)
[jira] [Updated] (STORM-2983) Some topologies not working properly
[
https://issues.apache.org/jira/browse/STORM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Li updated STORM-2983:
Description:
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
was:
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:
https://issues.apache.org/jira/browse/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
> 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
>Priority: Major
>
> 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)
