c38857e110
I don't see any obvious reason why we should wait ack/requeue is done. This waiter have already be removed from amqp1. https://git.openstack.org/cgit/openstack/oslo.messaging/tree/oslo_messaging/_drivers/amqp1_driver/controller.py#n242 So, this change remove it from rabbitmq driver too. Closes-bug: #1734788 Change-Id: I5ecedc762596181be19410b863851a0054fd6579
13 lines
619 B
YAML
13 lines
619 B
YAML
---
|
|
other:
|
|
- |
|
|
On rabbitmq, in the past, acknownlegement of messages was done within the
|
|
application callback thread/greenlet. This thread was blocked until the
|
|
message was ack. In newton, we rewrote the message acknownlegement to
|
|
ensure we haven't two threads writting the the socket at the same times.
|
|
Now all pendings ack are done by the main thread. They are no more reason
|
|
to block the application callback thread until the message is ack. Other
|
|
driver already release the application callback threads before the message
|
|
is acknownleged. This is also the case for rabbitmq, now.
|
|
|