From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Holding on to deleted packfiles
Date: Tue, 21 Sep 2021 16:57:56 -0400 [thread overview]
Message-ID: <20210921205756.2kgyln6kwwbncani@meerkat.local> (raw)
In-Reply-To: <20210921190653.GA16367@dcvr>
On Tue, Sep 21, 2021 at 07:06:53PM +0000, Eric Wong wrote:
> Was this from /all/ (ALL.git using batch-file) or Gcf2?
I believe this was from Gcf2, though I can't go back and check,
unfortunately.
> The old stuff has timers to do periodic cleanup, but the new
> stuff is trickier as the cost of a restart is higher...
>
> It should be alright to wire up the old timers to ALL.git with
> (hundreds) of inboxes lore currently has. git 2.33+ should be
> better when we get into the thousands; but it's still not
> great.
Well, it may also not be something that's the responsibility of public-inbox
either, e.g. other long-running daemons don't perform such checks. We can just
issue a reload after we've done repacking.
I was just wondering if perhaps you already did something that would recognize
that old pack files have gone away.
-K
next prev parent reply other threads:[~2021-09-21 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 14:47 Holding on to deleted packfiles Konstantin Ryabitsev
2021-09-21 19:06 ` Eric Wong
2021-09-21 20:57 ` Konstantin Ryabitsev [this message]
2021-09-21 21:37 ` Eric Wong
2021-09-22 9:45 ` [PATCH] gcf2 + extsearch: check for unlinked files on Linux Eric Wong
2021-09-22 19:51 ` Eric Wong
2021-09-23 0:46 ` [PATCH 2/1] daemons: revamp periodic cleanup task Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210921205756.2kgyln6kwwbncani@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).