summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlan Conway <aconway@apache.org>2012-02-13 14:09:56 +0000
committerAlan Conway <aconway@apache.org>2012-02-13 14:09:56 +0000
commit4689bcbf5ba9023a85393547304516b006b28c6e (patch)
tree837438c875348fa4ce7fc4094cac675290a63de5
parent96c469a3911d2f4669af0b618344c4feb277a59a (diff)
downloadqpid-python-4689bcbf5ba9023a85393547304516b006b28c6e.tar.gz
QPID-3603: minor updates to new-ha-design.txt
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/qpid-3603-2@1243524 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r--qpid/cpp/design_docs/new-ha-design.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/qpid/cpp/design_docs/new-ha-design.txt b/qpid/cpp/design_docs/new-ha-design.txt
index f1e9e240f1..8173585283 100644
--- a/qpid/cpp/design_docs/new-ha-design.txt
+++ b/qpid/cpp/design_docs/new-ha-design.txt
@@ -287,6 +287,14 @@ the requisite number of replication subscriptions established will be
confirmed to the publisher before they are replicated, leaving them
vulnerable to a loss of the new primary before they are replicated.
+LM6 - persistence: In the event of a total cluster failure there are
+no tools to automatically identify the "latest" store. Once this
+is manually identfied, all other stores belonging to cluster members
+must be erased and the latest node must started as primary.
+
+LM6 - persistence: In the event of a single node failure, that nodes
+store must be erased before it can re-join the cluster.
+
For configuration propagation:
LC2 - Queue and exchange propagation is entirely asynchronous. There
@@ -341,6 +349,7 @@ LC6 - The events and query responses are not fully synchronized.
It is not possible to miss a create event and yet not to have
the object in question in the query response however.
+
* Benefits compared to previous cluster implementation.
- Does not depend on openais/corosync, does not require multicast.