Previously, we have switched to use default exchanges
to avoid excessive amounts of exchange not found messages.
But it does not actually solve the problem because
reply_* queue is already gone and agent will not receive callbacks.
after some debugging, I found under some circumstances
seems rabbitmq consumer does not receive basic cancel
signal when queue is already gone. This might due to
rabbitmq try to restart consumer when queue is down
(for example when split brain). In such cases,
it might be better to fail early.
Reviewed: https:/ /review. opendev. org/747366 /git.openstack. org/cgit/ openstack/ oslo.messaging/ commit/ ?id=0a432c7fb10 7d04f7a41199fe9 a8c4fbd344d009
Committed: https:/
Submitter: Zuul
Branch: stable/ussuri
commit 0a432c7fb107d04 f7a41199fe9a8c4 fbd344d009
Author: shenjiatong <email address hidden>
Date: Fri Jul 3 15:51:21 2020 +0800
Cancel consumer if queue down
Previously, we have switched to use default exchanges
to avoid excessive amounts of exchange not found messages.
But it does not actually solve the problem because
reply_* queue is already gone and agent will not receive callbacks.
after some debugging, I found under some circumstances
seems rabbitmq consumer does not receive basic cancel
signal when queue is already gone. This might due to
rabbitmq try to restart consumer when queue is down
(for example when split brain). In such cases,
it might be better to fail early.
by reading the code, seems like x-cancel- on-ha-failover /github. com/rabbitmq/ rabbitmq- server/ blob/master/ src/rabbit_ channel. erl#L1894, /github. com/rabbitmq/ rabbitmq- server/ blob/master/ src/rabbit_ channel. erl#L1926.
is not dedicated to mirror queues only, https:/
https:/
By failing early, in my own test setup,
I could solve a certain case of exchange not found problem.
Change-Id: I2ae53340783e40 44dab58035bc099 2dc08145b53 0f82ec9e1c194ee f3f98fc0b1)
Related-bug: #1789177
(cherry picked from commit 196fa877a90d7eb