storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Devang Shah <>
Subject Re: bolt stop receiving tuples
Date Thu, 04 Dec 2014 12:22:20 GMT
Can you post your topology configuration here like the no. Of workers, no.
of instances of each spout/bolt, max pending spout etc.

What processing are you doing in the bolt B - connecting to external
service ? Try replacing all the code in execute method of bolt B with a log
statement and check if it's still an issue.

Thanks and Regards,
On 4 Dec 2014 19:28, "clay teahouse" <> wrote:

> This is a local cluster. I don't see anything interesting in the logs that
> would tell me anything.  I even removed Bolt A from the picture (meaning
> Spout->BoltB), and still Bolt B hangs, after the first pull. If that helps,
> the complete config is:
> spout-> Bolt B -> the remote non-storm entity that Bolt B sends data to.
> The interesting thing is that every time I restart the topology, one more
> tuple (of the backlog) is sent to the remote entity, and then the
> everything stops. So, if I restart the topology enough times (and the spout
> doesn't consume any new data), the remote server will ultimately get all
> the old tuples. It seems the tuples are buffered  and sent one by one to
> the remote entity, when the topology restarts.
> -Clay
> On Thu, Dec 4, 2014 at 3:25 AM, Vladi Feigin <> wrote:
>> Usually in such case you should start from looking the logs : supervisor
>> and worker
>> On Wed, Dec 3, 2014 at 6:09 PM, clay teahouse <>
>> wrote:
>>> Hello All,
>>> I have this configuration:
>>> spout -> Bolt A (emits tuples) -> Bolt B
>>> Bolt A emits tuples successfully but bolt B stops receiving tuples after
>>> the first time (it never enters the execute after the first time). The
>>> first time execution seems to be successful. Any idea what the issue could
>>> be or how trouble shoot the issue?
>>> thanks,
>>> Clay

View raw message