Skip to content

Commit 304e77d

Browse files
committed
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
2 parents 2a18f26 + 3d6ab41 commit 304e77d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

Documentation/git-maintenance.txt

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,9 @@ on an hourly basis. Each run executes the "hourly" tasks. At midnight,
220220
that process also executes the "daily" tasks. At midnight on the first day
221221
of the week, that process also executes the "weekly" tasks. A single
222222
process iterates over each registered repository, performing the scheduled
223-
tasks for that frequency. Depending on the number of registered
223+
tasks for that frequency. The processes are scheduled to a random minute of
224+
the hour per client to spread out the load that multiple clients might
225+
generate (e.g. from prefetching). Depending on the number of registered
224226
repositories and their sizes, this process may take longer than an hour.
225227
In this case, multiple `git maintenance run` commands may run on the same
226228
repository at the same time, colliding on the object database lock. This

0 commit comments

Comments
 (0)