Bug 473236
Summary: | 'Failed: Timed out waiting for broker to synchronize' issue (when qpidd run with switch --default-queue-limit) | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Frantisek Reznicek <freznice> |
Component: | qpid-cpp | Assignee: | messaging-bugs <messaging-bugs> |
Status: | NEW --- | QA Contact: | Kim van der Riet <kim.vdriet> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 1.1 | CC: | gsim |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Frantisek Reznicek
2008-11-27 10:10:13 UTC
Most likely due to the management queues needing a max depth greater than 1000 bytes for operation. Can we verify the limit at which the error appears? Frantisek verified correct operation with max depth of 10k bytes. Ted, can you work out a theoretically minimum allowed queue depth for correct operation of the management system? Maybe we should add a release note to communicate that? I'm targetting this for the next release as I feel there is a simple workaround and the impact of this is therefore minimal. However we perhaps want to consider whether management queues should set their own depths or some other way of handling this a bit more gracefully. |