aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2024-11-25 12:29:38 +0900
committerJunio C Hamano <gitster@pobox.com>2024-11-25 12:29:38 +0900
commit304e77d2f8fc6474281c0b767f5a918d036a0780 (patch)
treed317538400ee0257952fbe0423dc58c6def7eeda
parent2a18f26d77e89ecbe07f2d46e4ba91b309a6301d (diff)
parent3d6ab4177ddf63369ce3e7d12a0599724b6fa173 (diff)
downloadgit-304e77d2f8fc6474281c0b767f5a918d036a0780.tar.gz
Merge branch 'sk/doc-maintenance-schedule' into maint-2.47
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
-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