RPC calls and responses do not use the mandatory flag (AMQP)

Bug #1437955 reported by Attila Fazekas on 2015-03-29
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging
Wishlist
Gabriele Santomaggio

Bug Description

bit mandatory
---------------
This flag tells the server how to react if the message cannot be routed to a queue. If this flag is set, the server will return an unroutable message with a Return method. If this flag is zero, the server silently drops the message.

    The server SHOULD implement the mandatory flag.

bit immediate
----------------

This flag tells the server how to react if the message cannot be routed to a queue consumer immediately. If this flag is set, the server will return an undeliverable message with a Return method. If this flag is zero, the server will queue the message, but with no guarantee that it will ever be consumed.

===============================================================
https://www.rabbitmq.com/amqp-0-9-1-reference.html#basic.publish

Does not makes sense to wait for an rpc response, if the massage was dropped by broker or nobody reads it.

The rpc requests SHOULD be sent with 'mandatory' or 'immediate'.
The rpc response messages SHOULD be sent with 'immediate'.

It is probably just a small nit and does not makes a big difference in practice.

description: updated
Mehdi Abaakouk (sileht) on 2015-05-01
Changed in oslo.messaging:
status: New → Confirmed
importance: Undecided → Wishlist
Jay Pipes (jaypipes) on 2015-05-11
summary: - rpc calls and resonses does not uses at leat the mandatory flag (AMQP)
+ RPC calls and responses do not use the mandatory flag (AMQP)

It is worth to use the 'mandatory' flag during the publish, it also helps to understand/debug problems.

Currently oslo.messaging uses Kombu, the documentation says that the mandatory is not_supported, but I tried it and it works correctly.

I think that is generic information for all the AMQP brokers.

Asked here [1] for clarifications, waiting for an answer.
In the meantime, I am going to test it in oslo.

1 - https://github.com/celery/kombu/issues/1039

Ken Giusti (kgiusti) on 2019-04-29
Changed in oslo.messaging:
assignee: nobody → Gabriele Santomaggio (gsantomaggio)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.