take maxsize into account for balanced preferred content
This is very innefficient, it will need to be optimised not to calculate the sizes of repos every time. Also, fixed a bug in balancedPicker that caused it to pick a too high index when some repos were excluded due to being full.
This commit is contained in:
parent
b201792391
commit
745bc5c547
5 changed files with 60 additions and 11 deletions
|
@ -45,13 +45,15 @@ Planned schedule of work:
|
|||
Also note that "fullybalanced=foo:2" is not currently actually
|
||||
implemented!
|
||||
|
||||
* implement size-based balancing, either as the default or as another
|
||||
preferred content expression.
|
||||
* implement size-based balancing, so all balanced repositories are around
|
||||
the same percent full, either as the default or as another preferred
|
||||
content expression.
|
||||
|
||||
* `git-annex info` can use maxsize to display how full repositories are
|
||||
|
||||
* balanced= and fullybalanced= need to limit the set of repositories to
|
||||
ones with enough free space to contain a key.
|
||||
* --rebalance is not stable. It will drop a key that was just stored in a
|
||||
repo. Seems that limitFullyBalanced needs to take AssumeNotPresent
|
||||
into account to handle dropping correctly.
|
||||
|
||||
* Implement [[track_free_space_in_repos_via_git-annex_branch]]:
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue