diff options
author | Derrick Stolee <dstolee@microsoft.com> | 2020-10-15 17:22:04 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2020-10-16 08:36:42 -0700 |
commit | 0016b618182f642771dc589cf0090289f9fe1b4f (patch) | |
tree | b91beb5925cd585a0d0c8cd4ba65d7da34786cc6 /perl/Git/SVN/Prompt.pm | |
parent | maintenance: use 'incremental' strategy by default (diff) | |
download | tgif-0016b618182f642771dc589cf0090289f9fe1b4f.tar.xz |
maintenance: add troubleshooting guide to docs
The 'git maintenance run' subcommand takes a lock on the object database
to prevent concurrent processes from competing for resources. This is an
important safety measure to prevent possible repository corruption and
data loss.
This feature can lead to confusing behavior if a user is not aware of
it. Add a TROUBLESHOOTING section to the 'git maintenance' builtin
documentation that discusses these tradeoffs. The short version of this
section is that Git will not corrupt your repository, but if the list of
scheduled tasks takes longer than an hour then some scheduled tasks may
be dropped due to this object database collision. For example, a
long-running "daily" task at midnight might prevent an "hourly" task
from running at 1AM.
The opposite is also possible, but less likely as long as the "hourly"
tasks are much faster than the "daily" and "weekly" tasks.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'perl/Git/SVN/Prompt.pm')
0 files changed, 0 insertions, 0 deletions