[Spread-users] Spread for HA rpc services

Colin Meyer cmeyer at helvella.org
Wed Aug 8 16:09:05 EDT 2007

On Wed, Aug 08, 2007 at 02:14:41PM -0400, Daniel F. Savarese wrote:
> There are a number of different ways to do what you describe with 
> Spread, but you have to select the most appropriate algorithm for
> your application and implement it.  For example, one approach is
> for only the "leader" process to process the request, giving up
> leadership and passing it to the next available process.  Another
> approach is to implement a work queue and have each worker process
> ask the work queue/manager for work.  

Ok, this makes sense. Could you point me to any examples or recipes for
this sort of implementation?

It seems easy enough for the non-lead processes to ignore requests. What
happens when the current lead dies unexpectedly? The pool will receive
the disconnect message, but how do all of the processes come to a
consensus on which process is going to be the next lead?


More information about the Spread-users mailing list