storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Illecker <>
Subject Re: Urgent - Some workers stop processing after a few seconds
Date Wed, 25 Feb 2015 11:49:01 GMT

I'm still observing this strange issue.
Two of three workers stop processing after a few seconds. (each worker is
running on one dedicated EC2 node)

My guess would be that the output stream of one spout is not properly
distributed over all three workers.
Or somehow directed to one worker only? But *shuffleGrouping* should
guarantee equal distribution among multiple bolts right?

I'm using the following topology:

    TopologyBuilder builder = new TopologyBuilder();

    builder.setSpout("dataset-spout", spout);

    builder.setBolt("tokenizer-bolt", tokenizerBolt, 3).shuffleGrouping(


    builder.setBolt("preprocessor-bolt", preprocessorBolt,





        .submitTopology(TOPOLOGY_NAME, conf, builder.createTopology());

I have attached the screenshots of the topology and the truncated worker
and supervisor log of one idle worker.

The supervisor log includes a few interesting lines, but I think they are

supervisor [INFO] e76bc338-2ba5-444b-9854-bca94f9587b7 still hasn't started

I hope, someone can help me with this issue!

Best regards

2015-02-24 20:37 GMT+01:00 Martin Illecker <>:

> Hi,
> I'm trying to run a topology on EC2, but I'm observing the following
> strange issue:
> Some workers stop processing after a few seconds, without any error in the
> worker log.
> For example, my topology consists of 3 workers and each worker is running
> on its own EC2 node.
> Two of them stop processing after a few seconds. But they have already
> processed several tuples successfully.
> I'm using only one spout and shuffleGrouping at all bolts.
> If I add more spouts then all workers keep processing, but the performance
> is very bad.
> Does anyone have a guess why this happens?
> The topology is currently running at:
> Thanks!
> Martin

View raw message