[openstack-dev] [oslo.messaging] configurable ack-then-process (at least/most once) behavior
bdobrelia at mirantis.com
Wed Dec 2 11:01:17 UTC 2015
> Which service would use this flag to start with? and how would the
> code change to provide "app side is fully responsible for duplicates
(fixed topic tags to match oslo.messaging)
AFAIK, this mode is required by Mistral HA. Other projects may want
the at-least-once rpc delivery model as well.
I see that the patch scope is not enough. Although it would be nice to
have it demonstrated by the simple example... Anyway, we should address
all of the concerns raised here in the spec.
> On Tue, Dec 1, 2015 at 4:27 AM, Bogdan Dobrelya <bdobrelia at mirantis.com> wrote:
>> On 30.11.2015 14:28, Bogdan Dobrelya wrote:
>>> Please let's make this change  happen to the Oslo messaging.
>>> This is reasonable, straightforward and backwards compatible change. And
>>> it is required for OpenStack applications - see  - to implement a
>>> sane HA. The only thing left is to cover this change by unit tests.
>>>  https://review.openstack.org/229186
>> Here is related bp . I will submit the spec as well and put there all
>> of the concerns Mehdi Abaakouk provided in the aforementioned patch
>> review process. I believe the ack-then-process pattern *has* use cases,
>> that is why this topic will be raised again and again unless adressed.
>> Best regards,
>> Bogdan Dobrelya,
>> Irc #bogdando
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev