From: Andreas Krey <a.krey@gmx.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Flurries of 'git reflog expire'
Date: Thu, 6 Jul 2017 15:27:44 +0200 [thread overview]
Message-ID: <20170706132744.GA1216@inner.h.apk.li> (raw)
In-Reply-To: <87podgbkqi.fsf@gmail.com>
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
time ago.
> 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.
Andreas
--
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
next prev parent reply other threads:[~2017-07-06 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 7:57 Flurries of 'git reflog expire' Andreas Krey
2017-07-04 9:43 ` Ævar Arnfjörð Bjarmason
2017-07-06 13:27 ` Andreas Krey [this message]
2017-07-05 8:20 ` Jeff King
2017-07-06 13:31 ` Andreas Krey
2017-07-06 17:01 ` Bryan Turner
2017-07-11 4:45 ` Andreas Krey
2017-07-11 7:25 ` [BUG] detached auto-gc does not respect lock for 'reflog expire', was " Jeff King
2017-07-11 9:06 ` [PATCH] gc: run pre-detach operations under lock Jeff King
2017-07-12 16:46 ` Junio C Hamano
2017-07-12 16:58 ` Jeff King
2017-07-12 21:10 ` Junio C Hamano
2017-07-11 7:35 ` Flurries of 'git reflog expire' Bryan Turner
2017-07-11 7:45 ` Jeff King
2017-07-11 7:31 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170706132744.GA1216@inner.h.apk.li \
--to=a.krey@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).