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
[email protected]
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev

Reply via email to