On 12/11/2009 03:59 PM, Sandy Pratt wrote:
-----Original Message-----
From: Alan Conway [mailto:[email protected]]
Sent: Tuesday, November 24, 2009 7:56 AM
To: Jonathan Robie; qpid-dev-apache
Subject: [c++ cluster] User doc for persistent clusters.
I put up a user view of the peristent cluster changes, coming soon.
Would
appreaciate any feedback on the doc or the feature it describes.
http://cwiki.apache.org/confluence/display/qpid/Persistent+Cluster+Rest
art+Design+Note
Hi Alan,
Looks like a great step forward for clustering. Any hints on what's involved
in the manual intervention to enable restart from a full cluster crash? I'm
eager to kick the tires.
Basically it amounts to picking the "best" store and marking it clean by putting
a UUID in <data_dir>/cluster/shutdown.uuid, i.e. pretend it was shut down cleanly.
I'm working on providing some help to identify the "best" store and ultimately
hope to provide a tool for doing all this a bit more automatically. It will
probably mean running the tool on the data-directory of each cluster member
initially which is a pain - assumes remote logins or shared file systems.
I'd like to find a way to do this from one location without assuming shared
filesystems or remote logins. There was a suggestion that if there's a total
faliure the brokers come up in "admin mode" where they don't accept any clients
except an admin tool. The brokers would collect the info needed to pick the
clean store and mark it clean driven remotely by the admin tool. Does this sound
like a good direction, or do you have any other suggestions on how to approach this?
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
