summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-03-03 22:01:08 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-03-03 22:01:08 -0400
commit30ba218f4dec52134f8d0bd09dd9eba1de5a5333 (patch)
treedfba43cdf18ac4ba3591700d56067378b6e94000
parent8b300e36bd31fe62615afda8bc529a7e4d77904a (diff)
thundering herd
-rw-r--r--doc/design/iabackup.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/design/iabackup.mdwn b/doc/design/iabackup.mdwn
index b193e1f9d..215293879 100644
--- a/doc/design/iabackup.mdwn
+++ b/doc/design/iabackup.mdwn
@@ -221,3 +221,12 @@ A client could add other files to its local repo, and git-annex branch
pushes would include junk data about those files. It should probably be
filtered out by the git update hook (rejecting the whole push because of
this seems excessive).
+
+There may be a thundering herd problem, where many clients end up
+downloading the same Item at the same time, and more copies than neecessary
+result. The next `git annex sync --content` in some of the
+redundant clients will notice this and drop that item, and presumably
+download some other item. However, it might be good to rate limit the
+number of concurrent downloads of a given item, to prevent this and perhaps
+other issues. This could be done by a wrapper around git-annex shell or
+perhaps a git-annex modification.