Author: aconway
Date: Tue Oct 26 19:57:26 2010
New Revision: 1027714
URL: http://svn.apache.org/viewvc?rev=1027714&view=rev
Log:
Updates to new cluster design docs regarding active-passive mode.
Modified:
qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-active-passive.txt
qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-design.txt
qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-plan.txt
Modified: qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-active-passive.txt
URL:
http://svn.apache.org/viewvc/qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-active-passive.txt?rev=1027714&r1=1027713&r2=1027714&view=diff
==============================================================================
--- qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-active-passive.txt
(original)
+++ qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-active-passive.txt Tue Oct
26 19:57:26 2010
@@ -1,6 +1,10 @@
-*-org-*-
* Active/passive cluster implementation
+The active-active cluster can be used in an active-passive mode. In
+this mode we would like the cluster to be as efficient as a strictly
+active-passive implementation.
+
An active/passive implementation requires a subset of the active/active
approach:
- drop Queue ownership and locking
- replicate subset of Cluster interface, don't need to know all message
disposition.
@@ -18,8 +22,7 @@ Simpler implementation of broker::Cluste
Extra requirements:
- Passive members refuse client connections and redirect to active member.
- Choose new active member when the active dies.
-
-Question: How best to direct clients to the correct node after failover?
+- On failover, clients keep trying till they find the active member.
** Active/active vs. active passive
Modified: qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-design.txt
URL:
http://svn.apache.org/viewvc/qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-design.txt?rev=1027714&r1=1027713&r2=1027714&view=diff
==============================================================================
--- qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-design.txt (original)
+++ qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-design.txt Tue Oct 26
19:57:26 2010
@@ -326,6 +326,13 @@ queue replication', allowing such replic
on a WAN say) to be initiated after the queue had already been created
and been in use (one of the key missing features).
+** Optimizing the active-passive special case.
+
+In the case where all consumers of a queue are on the same broker, we
+can get better performance because we don't need to transfer ownership
+or information about acquisition. We need to optimize this case to
+perform like an active-passive mode of replication.
+
** Misc outstanding issues & notes
Replicating wiring
Modified: qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-plan.txt
URL:
http://svn.apache.org/viewvc/qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-plan.txt?rev=1027714&r1=1027713&r2=1027714&view=diff
==============================================================================
--- qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-plan.txt (original)
+++ qpid/trunk/qpid/cpp/src/qpid/cluster/new-cluster-plan.txt Tue Oct 26
19:57:26 2010
@@ -10,7 +10,8 @@ Co-existence with old cluster code and t
Minimal POC for message delivery & perf test.
- no wiring replication, no updates, no failover, no persistence, no async
completion.
- just implement publish and acquire/dequeue locking protocol.
-- measure performance.
+- optimize the special case where all consumers are on the same node.
+- measure performance: compare active-passive and active-active modes of use.
Full implementation of transient cluster
- Update (based on existing update), async completion etc.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:commits-subscr...@qpid.apache.org
