[tahoe-dev] uploading unhappiness error messages

Greg Troxel gdt at ir.bbn.com
Tue Jan 4 17:36:30 UTC 2011


If the server status page had information about which servers had
refused to take shares (and the smallest size that was refused)
recently, that would help people figure things out.   Right now the only
way to tell that servers are full is to get upload errors and then try
to piece things together.

servers-of-happiness isn't too complicated; the issue is that one really
wants a more complex "is this assignemnt adequately redundant"
predicate, taking both administrative and physical failure correlations
into account (and maybe something else).

Making the default be 1/10 would be ok.  I think the default needs to
admit redundancy even if it doesn't require it.  One can then change
From 1/1/10 to 1/3/10 just by changing configs, without any reencoding.
The initial setup should be one that can be migrated to a useful setup
without a restart.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110104/25e5e076/attachment.asc>


More information about the tahoe-dev mailing list