Thank you for the feedback.
I've juste switched back to 0.10 and I don't have the issue.
nextTuple is quite fast, I'm handleling a buffer of Tuple, when the buffer
is empty, I'm loading data from redis.
Ack method is deleting data on redis using pipeline to be fast.
It's strange that in the 0.1
nextTuple(), ack(), and fail() are all called by the same thread. nextTuple()
should be fast, so you probably only want to emit one or a handful of tuples.
Emitting a huge number of tuples in the nextTuple() method is what’s causing
your problem.
-Taylor
> On May 2, 2016, at 9:08 AM, Adrien Ca
Hi there,
Dont't know if I'm on the right place.. But let's try.
I'm build a Topology, And I've a spout plugged on Redis.
My question is, when the topology is active, Why the nextTuple() method
isn't call when ack() method is called.
Meaning, I've about 10k acking message without a nextTuple()
