Just to clarify my question regarding the ack: With the use case I mentioned, it should have said What is the default behavior with regard to acking in bolts and how the concept of offset and acking interact? Is it possible to not ack in a bolt to achieve the outcome I am looking for.
thanks. On Mon, Nov 17, 2014 at 12:49 PM, clay teahouse <[email protected]> wrote: > Hello All, > I am using kafka spout that comes with storm 0.9.3 ( > https://github.com/apache/storm). > I am having several different bolts consuming the same tuples from the > spout (in the same topology). These bolts process the tuples and send the > output to different destinations. I have a couple of basic questions: > 1) What happens if the destination for some of the bolts is not > accessible? I can have a mechanism in each bolt that returns without > consuming any tuple if the destination is not available. But what happens > to the tuples at hand and when is the next execute is invoked. > - Do I need to have the destination availability check in a loop? > - Do I need to keep track of the offset? > 2) Is it possible to ack in the bolts. > > thanks, > Clay >
