aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2024-10-10 14:22:26 -0700
committerJunio C Hamano <gitster@pobox.com>2024-10-10 14:22:26 -0700
commite29296745dc92fb03f8f60111b458adc69ff84c5 (patch)
treeed9577aa5f6faa5e0a29431cac5d42c02da2b950
parentMerge branch 'tb/notes-amlog-doc' (diff)
parentdoc: add a note about staggering of maintenance (diff)
downloadgit-e29296745dc92fb03f8f60111b458adc69ff84c5.tar.gz
git-e29296745dc92fb03f8f60111b458adc69ff84c5.zip
Merge branch 'sk/doc-maintenance-schedule'
Doc update to clarify how periodical maintenance are scheduled, spread across time to avoid thundering hurds. * sk/doc-maintenance-schedule: doc: add a note about staggering of maintenance
Diffstat (limited to '')
-rw-r--r--Documentation/git-maintenance.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/Documentation/git-maintenance.txt b/Documentation/git-maintenance.txt
index 9d96819133..6e6651309d 100644
--- a/Documentation/git-maintenance.txt
+++ b/Documentation/git-maintenance.txt
@@ -220,7 +220,9 @@ on an hourly basis. Each run executes the "hourly" tasks. At midnight,
that process also executes the "daily" tasks. At midnight on the first day
of the week, that process also executes the "weekly" tasks. A single
process iterates over each registered repository, performing the scheduled
-tasks for that frequency. Depending on the number of registered
+tasks for that frequency. The processes are scheduled to a random minute of
+the hour per client to spread out the load that multiple clients might
+generate (e.g. from prefetching). Depending on the number of registered
repositories and their sizes, this process may take longer than an hour.
In this case, multiple `git maintenance run` commands may run on the same
repository at the same time, colliding on the object database lock. This