[tahoe-dev] split brain? how handled in tahoe -- docs?

[Shawn Willden]

On Mon, Aug 6, 2012 at 5:12 PM, Tony Arcieri <tony.arcieri at gmail.com> wrote:

> An alternative to make it more robust would be to have vector clocks of
> which nodes modified which data. Tahoe could use this information to
> produce "siblings" in the event that the same file is modified by several
> parties. In the event of a conflict, a user could select which sibling they
> wished to use or perform their own conflict resolution. This is the
> approach used by Riak.
>

Even better would be to use a provably-correct distributed consistency
protocol, like Paxos.  But that's a lot of work.


-- 
Shawn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120806/45515a3b/attachment.html>