Ideally, each time nextTuple is called, you should be emitting only one
tuple. Of course, you can emit more than one, but then it would be better
to monitor the latency and emit only as many tuples which can be ack'ed
within a latency of 2.5 second.
Make sure you have enough of workers
Increase TOP
Hi Navin,
Yes, I meant by the sending rate; the outgoing tuples from the spout, as the
Representative for data source, to the computation bolts. The question about
tuning the respective parameters for increasing the spout emitting tuples.
Actually, I tried different values for max spout pending,
Please remember that we cannot read your mind. A little more elaboration on
what problem you are facing and what you mean by "sending rate" would help.
On Wed, Nov 23, 2016 at 5:56 PM, Walid Aljoby
wrote:
> Hi everyone,
>
> Could anyone has an experience to explain the factors affecting sending
Hi everyone,
Could anyone has an experience to explain the factors affecting sending rate in
Storm?
Thank you--RegardsWA
Hi,
We have been running STORM for a few months in production.
We started facing an issue with workers crashing all the time.
*2016-11-23 11:56:51.818 o.a.s.util [ERROR] Halting process: ("Worker
died")*
*java.lang.RuntimeException: ("Worker died")*
* at org.apache.storm.util$exit_process_BANG_.
Hi AI,
You can take a look at the `Container, Resource Management System
Integration` part in https://issues.apache.org/jira/browse/STORM-2209
Thanks,
Xin Wang (vesense)
2016-11-23 16:00 GMT+08:00 :
> Maybe http://highscalability.com/blog/2016/4/25/the-joy-of-
> deploying-apache-storm-on-docke
Maybe
http://highscalability.com/blog/2016/4/25/the-joy-of-deploying-apache-storm-on-docker-swarm.html
is also worth having a look at?
With kind regards
Samuel
-Original Message-
From: Marc Roos [mailto:m.r...@f1-outsourcing.eu]
Sent: Dienstag, 22. November 2016 19:44
To: user
Subjec
