Just to clarify: what we’re looking for is how to implement “Work queue” pattern described at [1] with oslo messaging. As Nikolay said, it requires that a message to be acknowledged after it has been processed. [1] http://www.rabbitmq.com/tutorials/tutorial-two-python.html <http://www.rabbitmq.com/tutorials/tutorial-two-python.html> Renat Akhmerov @ Mirantis Inc. > On 07 Jul 2015, at 15:58, Nikolay Makhotkin <nmakhotkin at mirantis.com> wrote: > > Hi, > > I am using RabbitMQ as the backend and searched oslo.messaging for message acknowledgement feature but I found only [1] what is wrong using of acknowledgement since it acknowledges incoming message before it has been processed (while it should be done only after processing the message, otherwise we can lost given message if, say, the server suddenly goes down). > > So, my questions: does oslo.messaging indeed not support correct acknowledgement feature? Or it is impossible to do for oslo.messaging paradighm? Or is it somehow connected with that oslo.messaging has to support a lot of transport types? > > Can't it be implemented somehow in oslo.messaging? > > [1] https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/dispatcher.py#L135 <https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/rpc/dispatcher.py#L135> > > > Best Regards, > Nikolay > @Mirantis Inc. > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150707/3dc46859/attachment.html>