Allow to configure the behavior of the rpc servers reconnection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.messaging |
Fix Released
|
High
|
Mehdi Abaakouk |
Bug Description
Currently all drivers reconnect to the rpc servers forever and this is not really configurable.
The rabbitmq driver allow to configure a max_retries value before raise a generic rpc_common.
But an application (ie: ceilometer) just needs to fail when all servers are not available instead of blocking forever and block the application (in the ceilometer use case, all swift requests are blocked until the server come back).
ie: ceilometer already have a hack/workaround to do this that using the max_retries of rabbitmq driver, see
https:/
Oslo.messaging needs a API to configure if the drivers should retry forever or just 1 times before raise a correctly named exception to the application.
This will allow to remove hack/workaround from ceilometer that use internal code of oslo.messaging and work only with rabbitmq
Cheers,
Changed in oslo.messaging: | |
assignee: | nobody → Mehdi Abaakouk (sileht) |
Changed in oslo.messaging: | |
importance: | Undecided → High |
Changed in oslo.messaging: | |
milestone: | none → juno-1 |
Changed in oslo.messaging: | |
milestone: | juno-1 → juno-2 |
Changed in oslo.messaging: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/75365
Review: https:/