Red Hat Bugzilla – Bug 876688
HA replication of propagated bindings can lead to incorrect configuration
Last modified: 2013-03-19 12:39:24 EDT
Description of problem:
When using dynamic federation between two independent HA broker clusters, it is possible under certain failover scenarios for the propagated bindings on the source broker to become out-of-sync with the true state of bindings on the destination broker.
Version-Release number of selected component (if applicable):
Often -- race condition between re-establishment of federated link and the deletion of a binding on the destination broker
Steps to Reproduce:
1. Start a stand-alone broker (route destination) and an HA broker (route source w/ primary and backup)
2. Configure a dynamic federated route between a destination broker and a source broker. The dynamic federation needs to utilize an existing, non-auto-delete queue on the source broker.
3. Subscribe to an auto-delete queue on the destination broker and bind the auto-delete queue to the exchange configured for the dynamic federation
4. Kill the primary source broker
5. Kill the subscription to the auto-delete queue on the destination broker
6. Promote the backup source broker to primary
With the loss of the client subscription to the auto-delete queue, the binding will be removed. If the binding is removed prior to the re-establishment of the federated link to the source broker, the unbind command will not propagate. Since the backup source broker had previously replicated the propagated binding, the binding will incorrectly remain on the source broker.
Propagated bindings should not be replicated from the primary to backups since they are transient and will be recreated when the route is re-established.
Created attachment 645040 [details]
Quick patch to exlude propagated bindings from replication
Reviewed and approve of the fix 0.18-mrg-crolke-bz876688