Opened at 2009-05-08T16:11:28Z
Last modified at 2015-10-29T01:58:58Z
#699 assigned defect
rebalance during repair or upload — at Version 4
| Reported by: | zooko | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | soon |
| Component: | code-peerselection | Version: | 1.4.1 |
| Keywords: | upload repair preservation test anti-censorship | Cc: | tahoe-lafs.org@… |
| Launchpad Bug: |
Description (last modified by davidsarah)
In this mailing list message, Humberto Ortiz-Zuazaga asks how to rebalance the shares of a file. To close this ticket, ensure (either as an option or unconditionally) that repairing or uploading a file attempts to "rebalance" its shares, making it healthy as defined by #614.
See also related tickets #481 (build some share-migration tools), #231 (good handling of small numbers of servers, or strange choice of servers), #232 (Peer selection doesn't rebalance shares on overwrite of mutable file.), and #543 ('rebalancing manager')
Change History (4)
comment:1 Changed at 2009-08-10T15:28:29Z by zooko
comment:2 Changed at 2009-08-10T15:45:34Z by zooko
Also related: #778 ("shares of happiness" is the wrong measure; "servers of happiness" is better).
comment:3 Changed at 2009-12-22T18:45:56Z by davidsarah
- Keywords repair preservation added
comment:4 Changed at 2010-03-24T23:26:36Z by davidsarah
- Description modified (diff)
- Keywords upload added
- Milestone changed from eventually to 1.7.0
- Summary changed from optionally rebalance during repair or upload to rebalance during repair or upload
- Type changed from enhancement to defect
It seems more usable for this behaviour to be unconditional rather than an option: why would you not want to attempt to ensure that a file is healthy (per #614) on a repair or upload?
The following clump of tickets might be of interest to people who are interested in this ticket: #711 (repair to different levels of M), #699 (optionally rebalance during repair or upload), #543 ('rebalancing manager'), #232 (Peer selection doesn't rebalance shares on overwrite of mutable file.), #678 (converge same file, same K, different M), #610 (upload should take better advantage of existing shares), #573 (Allow client to control which storage servers receive shares).