You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Simon Cooper <si...@featurespace.co.uk> on 2014/10/10 17:24:57 UTC
Tuple acked multiple times
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
RE: Tuple acked multiple times
Posted by Simon Cooper <si...@featurespace.co.uk>.
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: nathan.marz@gmail.com [mailto:nathan.marz@gmail.com] On Behalf Of Nathan Marz
Sent: 11 October 2014 03:51
To: user@storm.apache.org
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 <si...@featurespace.co.uk>> 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/>
Re: Tuple acked multiple times
Posted by Nathan Marz <na...@nathanmarz.com>.
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 <
simon.cooper@featurespace.co.uk> 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