mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

item splitting

Browse source
This commit is contained in:
Joey Hess 2015-03-03 21:49:41 -04:00
parent 979eace260
commit 8beeb1b4f1
1 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/design/iabackup.mdwn
View file

@ -21,7 +21,7 @@ them.
240 repositories.) 240 repositories.)
* The IA is ~20 Petabytes large. Each shard would thus be around 8 * The IA is ~20 Petabytes large. Each shard would thus be around 8
Terabytes. (However, Items sizes will vary a lot, so there's the Terabytes. (Item sizes will vary a lot, so there's the
potential to get a shard that's unusually small or large. This could be potential to get a shard that's unusually small or large. This could be
dealt with when assigning Items to the shards, to balance sizes out.) dealt with when assigning Items to the shards, to balance sizes out.)
@ -210,3 +210,9 @@ Clients will then download the new version of the Item.
Items sometimes go dark; this could be reflected by deleting the item Items sometimes go dark; this could be reflected by deleting the item
from the repository. It's up to the clients what they do with the content from the repository. It's up to the clients what they do with the content
of such Items. of such Items.
## other potential gotchas
If any single Item is very large (eg, 10 terabytes), there may not be
any clients that can handle it. This could be dealt with by splitting up
the item into smaller files.