[
https://issues.apache.org/jira/browse/QPID-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated QPID-4100:
------------------------------
Comment: was deleted
(was: Proposal to fix the bug:
1. For the security issue: stop using management for HA replication.
HA code will send store-encoded objects to a separate qpid.ha-replication
exchange.
Use ACL to restrict access to qpid.ha-replication to the replication user.
Benefits:
- solves the security problem
- separates HA from management, we don't have to bend management to suit HA.
- use store encoding, keep HA in sync with store which is a more logical match.
2. For the addressing issue: replicate changes of failover-url. The link on the
primary will connect and update its own failover-urls. Replicate those URLs to
the other brokers. )
> New HA federation links do not fail over
> ----------------------------------------
>
> Key: QPID-4100
> URL: https://issues.apache.org/jira/browse/QPID-4100
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Clustering
> Affects Versions: 0.17
> Reporter: Alan Conway
> Assignee: Cliff Jansen
>
> Given two new-HA clusters and a federation link between the primaries of each
> cluster:
> - if the source broker is killed, the route _does_ fail over to the new
> primary
> - if the destination broker is killed the route _is not_ re-created on the
> new primary
> Federation link and bridge information should be replicated to all cluster
> members so when a primary dies the backup that takes over can re-create links
> and bridges.
--
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: [email protected]
For additional commands, e-mail: [email protected]
