Ethan Li commented on STORM-2983:


Thanks very much for looking into it.


With ResourceAwareScheduler, the number of worker is actually calculated based 
on resources. `topology.workers` has no impact here.  As you pointed out, I 
believe the calculated `topology.workers` is not populated to Worker.


We do have the config `storm.scheduler`:  


> 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

Reply via email to