[
https://issues.apache.org/jira/browse/QPID-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway reopened QPID-4401:
-------------------------------
This issue has been raised again, there may be a way to fix it.
The problem is that the replica queue is bound to 2 active qmf exchanges, on
primary and on backup. Instead we could defer the binding on the backup until
that backup becomes a primary - mark them "primary only" bindings.
> New HA - bindings for QMF exchanges not replicated
> --------------------------------------------------
>
> Key: QPID-4401
> URL: https://issues.apache.org/jira/browse/QPID-4401
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Reporter: Andy Goldstein
> Assignee: Alan Conway
> Priority: Minor
>
> If I manually create a binding from qmf.default.topic to a queue, that
> binding is not replicated to backup brokers. When a failover occurs, the
> binding is gone.
> My use case, which is for a test harness, is that I have several
> active-passive broker clusters. Each active broker binds all queue-related
> events to a queue. A separate, standalone broker used to gather statistics
> uses a queue route to pull the queue-related QMF statistics from each
> cluster. In effect, I'm aggregating all QMF stats from all clusters into a
> single stats broker. When I initiate a failover for one of my clusters, I
> lose the binding for queue-related events, so I no longer get stats from that
> cluster.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
