[
https://issues.apache.org/jira/browse/STORM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420162#comment-16420162
]
Roshan Naik commented on STORM-2983:
------------------------------------
[~ethanli]
We have a problem in Storm with an excessive number of threads. See details in
STORM-2647 for how bad the issue is. In general, best to avoid having useless
threads lingering around as they are not free in terms of energy consumption in
in the long run and keep bumping off useful threads from their cores
periodically.
IMO, the right approach is to fix this by addressing the fundamental issue of
worker count reflecting the true state of the topology. Having the settings
reflect the right values is also useful for topologies (as they can query them
to find out the state of the topology). This would have to be fixed sooner or
later.
> 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)
