[
https://issues.apache.org/jira/browse/STORM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420273#comment-16420273
]
Roshan Naik edited comment on STORM-2983 at 3/30/18 8:20 AM:
-------------------------------------------------------------
[~kabhwan]
IMO this should not be viewed as a sidestepping an minor optimization. In which
case it does look like a minor issue. The optimization only exposed a bug. So
it is only the "messenger".
The key issue here is supporting (internal or user code) to check the state
correctly .. to do whatever it needs to do .... optimization or behavior
change.
By not fixing the core bug, we wlll sidestep the core issue. IMO this a
critical bug and needs to fixed. Or we need to provide a diff mechanism for
code to make such checks correctly.
was (Author: roshan_naik):
[~kabhwan]
IMO this should not be viewed as a sidestepping an optimization. In which case
it does look like a minor issue. The optimization only exposed a bug. So it is
only the "messenger".
The key issue here is supporting (internal or user code) to check the state
correctly .. to do whatever it needs to do .... optimization or behavior
change.
By not fixing the core bug, we wlll sidestep the core issue. IMO this a
critical bug and needs to fixed. Or we need to provide a diff mechanism for
code to make such checks correctly.
> 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)
