[
https://issues.apache.org/jira/browse/QPID-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated QPID-3603:
------------------------------
Description:
The existing cluster code suffers from some maintainability and performance
problems. This is a proposal to write a new HA solution based on the
"replicating subscription" that will replace the current cluster. This is a
competing proposal to QPID-2920.
Summary: a "replicating subscription" is a special queue browser that can see
acquired and un-acquired messages and also receives dequeue events to replicate
remote queue contents. The new HA solution will create & manage these
subscriptions in order to maintain a back-up of a primary broker on one or more
back-up brokers. This is an active-passive hot-standby configuration, where
exactly one broker is primary and the others are secondary. Initially plan is
to use Cluster Suite's rgmanager to enforce the roles and manage fail-over, but
we could support other cluster resource managers (e.g. PaceMaker) in the future.
was:
The existing cluster code suffers from some maintainability and performance
problems. This is a proposal to write a new HA solution based on the
"replicating subscription" that will replace the current cluster. This is a
competing proposal to QPID-2920. Some design notes are at
https://svn.apache.org/repos/asf/qpid/trunk/qpid/cpp/design_docs/hot-standby-design.txt
Summary: a "replicating subscription" is a special queue browser that can see
acquired and un-acquired messages and also receives dequeue events to replicate
remote queue contents. The new HA solution will create & manage these
subscriptions in order to maintain a back-up of a primary broker on one or more
back-up brokers. This is an active-passive hot-standby configuration, where
exactly one broker is primary and the others are secondary. Initially plan is
to use Cluster Suite's rgmanager to enforce the roles and manage fail-over, but
we could support other cluster resource managers (e.g. PaceMaker) in the future.
> New approach to HA
> ------------------
>
> Key: QPID-3603
> URL: https://issues.apache.org/jira/browse/QPID-3603
> Project: Qpid
> Issue Type: Improvement
> Affects Versions: 0.14
> Reporter: Alan Conway
> Assignee: Alan Conway
>
> The existing cluster code suffers from some maintainability and performance
> problems. This is a proposal to write a new HA solution based on the
> "replicating subscription" that will replace the current cluster. This is a
> competing proposal to QPID-2920.
> Summary: a "replicating subscription" is a special queue browser that can see
> acquired and un-acquired messages and also receives dequeue events to
> replicate remote queue contents. The new HA solution will create & manage
> these subscriptions in order to maintain a back-up of a primary broker on one
> or more back-up brokers. This is an active-passive hot-standby configuration,
> where exactly one broker is primary and the others are secondary. Initially
> plan is to use Cluster Suite's rgmanager to enforce the roles and manage
> fail-over, but we could support other cluster resource managers (e.g.
> PaceMaker) in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
