[Spread-users] Handling splits and joins in replication

Ryan Caudy rcaudy at gmail.com
Wed Apr 18 23:21:39 EDT 2007

There are some papers about how to do this sort of thing on
Maybe http://www.cnds.jhu.edu/pub/papers/AT02_icdcs.pdf would be a good one
to start with, but it may be that Yair has a different suggestion.


On 4/18/07, Nick Johnson <arachnid at notdot.net> wrote:
> I have a simple event server that keeps a list of all events sent to a
> particular event queue, and allows clients to ask for ranges. I'm
> wanting to implement replication for load-balancing and reliability
> using Spread. In order for clients to be able to know that they have
> every event, the order of events on each replicated server needs to be
> identical. The basic replication using Spread is easy. What I'm unsure
> about is how to handle splits/joins.
> Has anyone had to deal with this issue? How do you ensure that if a
> split occurs, the individual servers won't become out of sync and each
> accept events that cannot be merged when a join occurs, without
> relying on a single authoritative server (which is hence vulnerable to
> failure)?
> -Nick Johnson
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.spread.org/pipermail/spread-users/attachments/20070418/e05cde91/attachment.html 

More information about the Spread-users mailing list