max spout pending

[Shepherd Kendall <sh...@newbrandanalytics.com>]

Hey all --

I asked a similar question a few weeks ago, but wanted to frame the
question in a different way.

We have implemented a custom spout which polls a RabbitMQ queue for
messages.  The spout anchors the tuple and emits it to the bolt.  Once the
bolt receives the tuple and finishes processing, we send an ack on that
tuple.  The ack is received just fine, but when we set max spout pending to
anything but 1 and the message stream stops, we have pending ack's
remaining in the topology that have not been sent.

I assume this is due to the design of the RotatingMap.  I see that the
RotatingMap is configured with 2 buckets, and I assume that the dead bucket
(last bucket) is not cleared until a call is made to rotate().

Is there a configuration parameter we can call that would call rotate() and
clear all remaining ack'ed tuples in the topology?

-- 
/shep