qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marnie McCormack (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Updated: (QPID-33) Introduce clustering for high availability & fault tolerance
Date Tue, 31 Oct 2006 14:56:28 GMT
     [ http://issues.apache.org/jira/browse/QPID-33?page=all ]

Marnie McCormack updated QPID-33:

    Fix Version/s: M2

> Introduce clustering for high availability & fault tolerance
> ------------------------------------------------------------
>                 Key: QPID-33
>                 URL: http://issues.apache.org/jira/browse/QPID-33
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>            Reporter: Marnie McCormack
>             Fix For: M2
> This task has been created as an initial place holder from which it is anticipated many
tasks will derive.
> We currently have a clustering implementation which provides scalability but not high
availability i.e. currently if a broker in a cluster fails its clients can failover to another
broker in the same cluster BUT we do not have the ability to restart on another node at the
last state before failure using the saved state (from shared storage). 
> The other brokers in a cluster will know about (via broadcasting) each other's queues
etc, but not about any action the failed broker will processing - thus we could potentially
suffer message loss and state disconnect. Also note that currently membership of a cluster
does not imply any failover behaviour automatically.
> We know that there are users who require HA/fault tolerant clustering with 99.999% availability.
> A holding page for clustering & HA notes exists here: http://wiki.apache.org/qpid/ClusteringHA
with use case content.
> The analysis for this task will involve expanding the design documentation and inviting
review prior to work starting on the implementation and also requires a thorough understanding
of the protocol.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message