summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlan Conway <aconway@apache.org>2012-02-28 15:28:04 +0000
committerAlan Conway <aconway@apache.org>2012-02-28 15:28:04 +0000
commit787d974a36dfd5d70dc49fb3693f0f4a494653d1 (patch)
treecf3b5a684945d83c0a5933e8091a87aa77d5f5ea
parent9ed8af889ffb0bb347eb469787c50fa173a6a9a9 (diff)
downloadqpid-python-787d974a36dfd5d70dc49fb3693f0f4a494653d1.tar.gz
QPID-3603: Update HA design doc comments on persistence.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1294691 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r--cpp/design_docs/new-ha-design.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/cpp/design_docs/new-ha-design.txt b/cpp/design_docs/new-ha-design.txt
index 3272b1315f..24e28122f8 100644
--- a/cpp/design_docs/new-ha-design.txt
+++ b/cpp/design_docs/new-ha-design.txt
@@ -288,12 +288,12 @@ 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.
+no tools to automatically identify the "latest" store.
-LM6 - persistence: In the event of a single node failure, that nodes
-store must be erased before it can re-join the cluster.
+LM7 - persistence: In the event of a persistent broker being
+re-started (due to failure or admin) it should be able to use its
+stored messages to reduce the download required from the
+primary. This means storing message IDs persistently.
For configuration propagation: