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

Tue Aug 7 01:23:23 UTC 2012

On 07/08/12 01:23, Shawn Willden wrote:
> On Mon, Aug 6, 2012 at 5:12 PM, Tony Arcieri <tony.arcieri at gmail.com
> <mailto: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.

The 2-phase commit we've been talking about
(https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1755 , although that doesn't have much
detail) is essentially a special case of Paxos with a gateway acting as both Proposer
and (single) Learner, and the servers acting as Acceptors.

-- 
David-Sarah Hopwood ⚥

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120807/f588a9f4/attachment.pgp>