[tahoe-dev] Real-world Tahoe-LAFS grid deployment

Zooko O'Whielacronx zooko at zooko.com
Mon Nov 15 05:58:23 UTC 2010


Yeah, more detailed control over share location would definitely be
useful. See wiki:ServerSelection and related tickets.

I wouldn't consider it be a complete replacement for "erasure coding
with large values of N and (N-K)" though, because something could go
wrong outside of the model that you used. You might configure it to
distribute shares across data centers and across racks, but then get
hit by a kernel bug or something that wipes out all of your
even-numbered disks on all machines, or some other such weird pattern,
and therefore lose files.

Having a large N and a not-too-small N-K is a hedge against such
unanticipated failures, so I think of the two approaches as good
complements to one another.

It would indeed be great if someone would volunteer to implement the
wiki:ServerSelection features!

Regards,

Zooko

[1] http://tahoe-lafs.org/trac/tahoe-lafs/wiki/ServerSelection


More information about the tahoe-dev mailing list