** Changed in: oslo.messaging
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1437902
Title:
nova redeclares the `nova` named exchange zillion times without a real
need
Status in OpenStack Compute (Nova):
Incomplete
Status in Messaging API for OpenStack:
Fix Released
Bug description:
The AMQP broker preserves the exchanges, they are replaced to all broker even
in non HA mode.
A transient exchange can disappear ONLY when the user explicitly requests
it's deletion or when the full rabbit cluster dies.
More efficient to declare exchanges only when it is really missing.
Application MUST redeclare the exchange when it was reported as Not Found.
Note.: The Channel exceptions causes channel termination, but not connection
termination.
Application MAY try to redeclare the exchange on connection breakage, it can
assume the messaging cluster dead.
Application SHOULD redeclare the exchange at application start up to verify
the attributes (Before the first usage).
Application does not needs to redeclare the exchange in any other cases.
Now, significant amount of the AMQP request/response-es is
Exchange.Declare -> Exchange.Declare-Ok. (One per publish?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1437902/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
