Looks like you got bit by the same bug I did. Are you using storm 0.9.2? That error has nothing to do with acking. You get it because the offset requested is to old. See https://github.com/apache/storm/pull/183
Set spoutConf.maxOffsetBehind = Long.MAX_VALUE To fix this error. On Thursday, November 27, 2014, Fabiano Francesconi < [email protected]> wrote: > Hi all, > very quick question for you. What happens if you ack a tuple twice? Does > storm keep track of acked tuples? > > I had this very strange situation in which the kafka spout was failing > tuples with the message: > > Skipping failed tuple at offset=6760842181 because it's more than > maxOffsetBehind=1000000 behind _emittedToOffset=6762385621 > > > > After double-checking the code, I saw that we were acking a tuple twice. > We fixed the bug and now everything seems fine but I am not convinced with > the solution. > > What do you guys think? > > Regards, > Fabiano Francesconi >
