Bug 1312912
Summary: | Option "rabbit_retry_backoff" from component config has no effect when autoretrying connection | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marian Krcmarik <mkrcmari> | |
Component: | python-oslo-messaging | Assignee: | Flavio Percoco <fpercoco> | |
Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 8.0 (Liberty) | CC: | apevec, jschluet, lhh, tbarron, vstinner, yeylon | |
Target Milestone: | ga | |||
Target Release: | 8.0 (Liberty) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | python-oslo-messaging-2.5.0-5.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
When the RabbitMQ service fails to deliver an AMQP message from one OpenStack service to another, it reconnects and retries delivery. The "rabbit_retry_backoff" option, whose default is 2 seconds, is supposed to control the pace of retries; however, retries were previously done every second irrespective of the configured value of this option. The consequence of this problem was excessive retries, for example, when an endpoint was not available. This problem has now been fixed, and the "rabbit_retry_backoff" option, as explicitly configured or with the default value of two seconds, properly controls message delivery retries.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1313522 (view as bug list) | Environment: | ||
Last Closed: | 2016-04-07 21:31:44 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1313522 |
Description
Marian Krcmarik
2016-02-29 14:03:24 UTC
python-oslo-messaging-2.5.0-5.el7ost is ready for tests. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0603.html |