[rabbitmq-discuss] Ack by a different machine than consumer

Fri Dec 10 01:21:52 GMT 2010

Let's just say I'm working on the "Cascalog for stream-processing",
although the semantics of the tool will be quite different of course.
The goal is to be able to do distributed stream processing with the
details of fault tolerance and messaging abstracted away. The rest I'm
keeping secret for now :)

Alternatively, is it possible to ack messages out of order from how
you read them off the queue? Also, is it possible to set a timeout on
acking a message, so that if a message isn't acked within X secs it's
automatically considered failed and scheduled for redelivery?

Thanks,
Nathan

On Dec 9, 5:11 pm, Jerry Kuch <jer... at vmware.com> wrote:
> Hi, Nathan...
>
> I believe the delivery tag you'd use in ack-ing is only valid within the channel in which the message was received so the scheme you propose wouldn't be viable and you'd have to devise some scheme for signifying done-ness with the message's implied work beyond basic AMQP.
>
> BTW, Cascalog is a neat piece of work.  Would be interested to know more about the system you're building if it's not confidential...   :-)
>
> Jerry
>
> Sent from my iPhone (Brevity and typos are hopefully the result of 1-fingered typing rather than rudeness or illiteracy).
>
> On Dec 9, 2010, at 4:47 PM, "nathanmarz" <nathan.m... at gmail.com> wrote:
>
> > Can a message be ack'd by a different machine than the one that read
> > it off the queue?
>
> > I'm working on a distributed stream processing system where it would
> > be useful to have a downstream node do the acknowledgement.
>
> > Thanks in advance,
> > Nathan
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-disc... at lists.rabbitmq.com
> >https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss