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
This commit is contained in:
@ -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
|
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
|
of the week, that process also executes the "weekly" tasks. A single
|
||||||
process iterates over each registered repository, performing the scheduled
|
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.
|
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
|
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
|
repository at the same time, colliding on the object database lock. This
|
||||||
|
Reference in New Issue
Block a user