user@storm.apache.org
Subject: RE: Storm Topology Hanging
Hi Nitin,
You might get problems with max spout pending if you delay acking of one
message until another arrives. In this case having a low max spout pending can
cause the buffers to fill before the awaited message arrives. But this type of
dead
e-zest.in]
> *Sent:* Wednesday, April 06, 2016 1:30 PM
> *To:* user@storm.apache.org
> *Subject:* RE: Storm Topology Hanging
>
>
>
> Thanks for the response!
>
>
>
> · The Storm version is 0.9.4
>
> · I have set a message timeout to 300 second
Try to check the log of kafka at the moment topology began to hung, and the
load of kafka cluster at that moment. I met a situation is that the kafka is
too busy to response, it cause storm topology hung, especially when you use
transactional topology.
lujinhong
> 在 2016年4月7日，13:58，Nitin
Hi Nitin,
Though it decreases throughput when max spout pending value is small, it
should not hang.
Which version of Storm do you use, and could you share stack trace of
workers if you don't mind?
Btw, your spout latency is a bit high (10s). Which value you set message
timeout secs?
Thanks,
Dear All,
I am facing an issue where in one of my Topology hangs after 14-16 hours.
>From the Storm UI I can see the below statics:
* Number of Records Emitted: 4000
* Number of Records Acked : 3180
* Number of Records Failed : 1140
* The Spout Latency is
