| | 20 | |
| | 21 | == Share Rebalancing and Repair == |
| | 22 | |
| | 23 | Tahoe-LAFS is not as robust with regards to lost or corrupted shares as it could be. In part, this is because the repair functionality is limited in its efforts to spread shares out among new servers or servers which did not previously hold a given share (#699, #1130). In addition, mutable files do not spread out to new servers upon modification (#232). The servers-of-happiness metric is also not uniformly applied, with some operations succeeding even though an entity is not happy ([https://tahoe-lafs.org/trac/tahoe-lafs/query?status=!closed&keywords=~servers-of-happiness&order=priority bugs]). |
| | 24 | |
| | 25 | A Summer of Code project might tackle repair and rebalancing, ensuring that servers-of-happiness is met whenever possible on any upload, repair, or mutable modification. The notes on ServerSelection and related configurations may also be relevant here. |
