Bug 491305
| Summary: | clustered qpidd - replicating non-acked messages is not made visible for managent tools qpid-tool/cumin | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Frantisek Reznicek <freznice> |
| Component: | qpid-cpp | Assignee: | mick <mgoulish> |
| Status: | CLOSED ERRATA | QA Contact: | Frantisek Reznicek <freznice> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.1 | CC: | esammons, gsim |
| Target Milestone: | 1.3 | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When a new broker joined a cluster, messages to the cluster which had been acquired—but not yet either accepted or released—were not communicated to the new broker. As a result, the graphical management tools could have shown state inaccuracies. This update ensures that non-completed messages and queue properties are replicated to newly-joined cluster members, with the result that new broker state no longer occasionally diverges.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-14 16:14:24 UTC | 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
2009-03-20 10:22:38 UTC
Fixed (primarily by r779183).
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause:
When a new broker joins a cluster, messages to the cluster that had been acquired but had not yet been either accepted or released were not being communicated to the newbie.
Consequence:
Several aspects of broker state ( store state, policy state, mgmt stats ) could be inaccurate in the newbie.
Fix:
Make sure that non-completed messages -- as well as all queue properties -- are replicated to newly joining cluster members.
Result:
The state of clustered brokers viewable in management tools no longer occasionally diverges.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,13 +1 @@
-Cause:
+When a new broker joined a cluster, messages to the cluster which had been acquired—but not yet either accepted or released—were not communicated to the new broker. As a result, the state of the newly-joined broker could have shown inaccuracies in the management tools. This update ensures that non-completed messages and queue properties are replicated to newly-joined cluster members, with the result that new broker state no longer occasionally diverges.-When a new broker joins a cluster, messages to the cluster that had been acquired but had not yet been either accepted or released were not being communicated to the newbie.
-
-Consequence:
-Several aspects of broker state ( store state, policy state, mgmt stats ) could be inaccurate in the newbie.
-
-
-Fix:
-Make sure that non-completed messages -- as well as all queue properties -- are replicated to newly joining cluster members.
-
-
-Result:
-The state of clustered brokers viewable in management tools no longer occasionally diverges.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-When a new broker joined a cluster, messages to the cluster which had been acquired—but not yet either accepted or released—were not communicated to the new broker. As a result, the state of the newly-joined broker could have shown inaccuracies in the management tools. This update ensures that non-completed messages and queue properties are replicated to newly-joined cluster members, with the result that new broker state no longer occasionally diverges.+When a new broker joined a cluster, messages to the cluster which had been acquired—but not yet either accepted or released—were not communicated to the new broker. As a result, the graphical management tools could have shown state inaccuracies. This update ensures that non-completed messages and queue properties are replicated to newly-joined cluster members, with the result that new broker state no longer occasionally diverges.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0773.html |