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

[Two Spirit]

well, let me back up one then, if two remote offices share a directory, and
the connectivity between them gets disconnected, each side thinks it just
lost half its repository, then you site1 adds file1, and site2 adds file2
to their respective halfs, not knowing the other site is not connected.
when they connect back up, what happens? do you at least have a file1 and
file2 in the same place. I won't even start with the more complicated
scenarios right now. It sounds like tahoe is more designed for a single
user from a single location utilizing remote encrypted data-stores for that
single user. Am I getting closer?

On Fri, Aug 3, 2012 at 12:33 PM, erpo41 at gmail.com <erpo41 at gmail.com> wrote:

> Afaik, tahoe doesn't handle multiple users updating the same file at the
> same time. If you have two workers in two offices working on the same file
> at the same time, they had better be calling each other on the phone while
> they're doing it.
> On Aug 3, 2012 12:13 AM, "Two Spirit" <twospirit6905 at gmail.com> wrote:
>
>> Is there any docs how the "split-brain" scenario is handled with tahoe
>> where the distributed data stores get split in two halves and both halves
>> are working independent of each other, and any file changes cause each half
>> to become divergent.
>>
>> Maybe a simple scenario is two remote corporate sites loose connectivity
>> between sites, and each site thinks they are the complete network and both
>> sides start modifying the same files, then connection is re-established
>> later.
>>
>> _______________________________________________
>> tahoe-dev mailing list
>> tahoe-dev at tahoe-lafs.org
>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>
>>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120803/d74f60d7/attachment.html>