Ah yes, that was it. We’ve got a spout that emits to 2 streams for one ‘input’ message, and we were using the same message id for tuples emitted to both streams. Thanks!
From: [email protected] [mailto:[email protected]] On Behalf Of Nathan Marz Sent: 11 October 2014 03:51 To: [email protected] Subject: Re: Tuple acked multiple times No Storm will not do that. Are you sure you're not assigning the same message id to multiple tuples. On Fri, Oct 10, 2014 at 8:24 AM, Simon Cooper <[email protected]<mailto:[email protected]>> wrote: We’re seeing a puzzling behaviour where the same tuple is acked several times at the spout. This is causing problems, as we’ve assumed each tuple is only acked once. Is it valid for storm to ack the same message id several times, or have we screwed up the topology somewhere? In what situations might this happen? Thanks, SimonC -- Twitter: @nathanmarz http://nathanmarz.com<http://nathanmarz.com/>
