Re: Flurries of 'git reflog expire'
- Date: Thu, 6 Jul 2017 15:27:44 +0200
- From: Andreas Krey <a.krey@xxxxxx>
- Subject: Re: Flurries of 'git reflog expire'
On Tue, 04 Jul 2017 11:43:33 +0000, Ævar Arnfjörð Bjarmason wrote:
> You can set gc.auto=0 in the repo to disable auto-gc, and play with
> e.g. the reflog expire values, see the git-gc manpage.
> But then you need to run your own gc, which is not a bad idea anyway
> with a dedicated git server.
Actually, bitbucket should be doing this. Although I can't quite
rule out the possibility that we reenabled GC in this repo some
> But it would be good to get to the bottom of this, we shouldn't be
> running these concurrently.
Indeed. Unfortunately this isn't easily reproduced in the test instance,
so I will need to get a newer git under the production bitbucket.
There are quite some of
\_ /usr/bin/git receive-pack /opt/apps/atlassian/bitbucket-data/shared/data/repositories/68
| \_ git gc --auto --quiet
| \_ git reflog expire --all
in the process tree, apparently a new one gets started even though previous
ones are still running. The number of running expires grew slowly, in the
order of many minutes.
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800