summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-03-03 21:49:41 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-03-03 21:49:41 -0400
commitc00c962c67ae13ff00a12599b26ea6106b2bd207 (patch)
tree0ab2e8eadddbc9df4142e0a131a92852d0cac0a4
parent048622219f48d2cc7c95556da0b5966ef30334ad (diff)
item splitting
-rw-r--r--doc/design/iabackup.mdwn8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/design/iabackup.mdwn b/doc/design/iabackup.mdwn
index 56f7486f0..68940cb4f 100644
--- a/doc/design/iabackup.mdwn
+++ b/doc/design/iabackup.mdwn
@@ -21,7 +21,7 @@ them.
240 repositories.)
* 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
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
from the repository. It's up to the clients what they do with the content
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.