stop seeing tick tuples in the log.
collector.ack(input);
is at the end of every one execute() method.
--
Tomas Mazukna
678-557-3834
take a thread dump and check if storm's executor threads
are stuck on a blocking call.
On Wed, Sep 24, 2014 at 2:24 AM, Tomas Mazukna tomas.mazu...@gmail.com
wrote:
config.put(Config.TOPOLOGY_TICK_TUPLE_FREQ_SECS, 60);
submit topology and after about 4 hours tick tuples just stop
in general is a costly operation?
Thanks,
Tomas
On Wed, Jul 23, 2014 at 2:35 PM, Tomas Mazukna tomas.mazu...@gmail.com
wrote:
No, its on RHE on real hardware...
Although we went through a network upgrade couple day ago and all sort of
things started failing
On Wed, Jul 23, 2014 at 1:43
to another similar thread)
-AM
On Jul 23, 2014 10:07 AM, Tomas Mazukna tomas.mazu...@gmail.com wrote:
I am really puzzled why processing stopped in the topology.
Looks like the acking threads all stopped communicating. Only hint I saw
was this netty exception:
Any hints how to prevent
of the grouping defined
(as grouping from my understanding is for bolt *tasks* not actual bolts).
I've searched a bit and I can't seem to find a way to accomplish that...
is there a way to do that or I am searching in vain?
Thanks.
--
Tomas Mazukna
678-557-3834
at 2:33 AM, Tomas Mazukna
tomas.mazu...@gmail.com wrote:
Andrew,
when you connect your bolt to your spout you specify the grouping. If
you use shuffle grouping then any free bolt gets the tuple - in my
experience even in lightly loaded topologies the distribution amongst
bolts
is pretty
set in the spout which kafka partition to
subscribe at?
Kindly yours,
Andrew Grammenos
-- PGP PKey --
https://www.dropbox.com/s/2kcxe59zsi9nrdt/pgpsig.txt
https://www.dropbox.com/s/ei2nqsen641daei/pgpsig.txt
On Thu, Jul 17, 2014 at 3:30 AM, Tomas Mazukna tomas.mazu...@gmail.com
wrote
execute the topology.
how can i do it?
Thanks,
Lax
--
Tomas Mazukna
678-557-3834
the KafkaSpout to talk to zookeeper ?
Thanks,
Josh
--
Tomas Mazukna
678-557-3834
, Tomas Mazukna tomas.mazu...@gmail.com
wrote:
We have 4 kafka brokers, each topic is replication factor 3. For a heavy
loaded topic we have 40 partitions.
I wrote Kafka Spout which uses Kafka group reader API to emit tuples.
Running 40 spout instances each is connected to a single partition
If a spout receives fail on the message, will storm replay the message, or
spout needs to re-emit it again?
--
Tomas Mazukna
11 matches
Mail list logo