Mehdi Abaakouk da02bc2169 rabbit: restore synchronous ack/requeue
In https://review.openstack.org/#/c/436958, we fix a thread safety
issue. But we make the ack/requeue of message asynchronous. In nominal
case, it works, but if network/rabbit connection issue occurs this
can result to rpc call handle twice. By chance we double check already
processed message ids, and drop duplicates, but that if the message
goes to another node, the mitigation won't work.

This restore the previous behavior, to ensure we run application
callback of rpc.call/rpc.cast only when the message have been
successfully ack.

Change-Id: I62b9e09513e3ebfebc64a941d4b21b6c053b511d
2017-05-21 11:42:41 +02:00
2015-09-24 18:11:22 +08:00
2017-03-30 12:32:58 +00:00
2014-06-05 22:48:44 +02:00
2017-01-02 11:34:02 +01:00
2017-04-08 22:39:02 +08:00
2017-04-08 22:39:02 +08:00
2017-04-08 22:39:02 +08:00
2017-03-16 15:22:18 +00:00
2017-03-04 01:51:17 +00:00

Team and repository tags

image

Oslo Messaging Library

Latest Version

Downloads

The Oslo messaging API supports RPC and notifications over a number of different messaging transports.

Description
OpenStack library for messaging
Readme 36 MiB
Languages
Python 99.8%
Shell 0.2%