[
https://issues.apache.org/jira/browse/STORM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424755#comment-16424755
]
Jungtaek Lim commented on STORM-2983:
-------------------------------------
I'm still +1 to the proposed fix. Even better if we can avoid removing the
optimization code with determining there's outgoing connection, but it's OK to
skip if it is not trivial.
Topology configuration is what users set up the values, and users will get
confused if some of them are dynamically updated. And we already know that not
all the configurations may be valid according to the scheduler.
"topology.workers" is popular one so it doesn't look trivial to ignore such
value, but I think we can explain why it is ignored in RAS document.
If we really want to maintain runtime status, better to have separated one
instead of modifying topology configuration to retain users' input.
> 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)
