From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: V2 shard roll-over
Date: Tue, 12 Feb 2019 19:27:15 +0000 [thread overview]
Message-ID: <20190212192715.mtncyagjzusi3vtp@dcvr> (raw)
In-Reply-To: <20190212191116.GA8720@chatter.qube.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Eric:
>
> I noticed today that the LKML shard 6 has grown over 1.1 GB, which is the
> size of other shards (0-5). I'm wondering if it will roll over to shard 7
> automatically, or if there are other steps that need to be undertaken.
It only counts bytes in *.pack files; so you might need to repack
(or wait for gc to run via --auto).
You can monitor the rollover via stderr with the following to be
sure:
diff --git a/lib/PublicInbox/V2Writable.pm b/lib/PublicInbox/V2Writable.pm
index 1f17fe2..0fd8c60 100644
--- a/lib/PublicInbox/V2Writable.pm
+++ b/lib/PublicInbox/V2Writable.pm
@@ -588,6 +588,9 @@ sub importer {
if (defined $latest) {
my $git = PublicInbox::Git->new($latest);
my $packed_bytes = $git->packed_bytes;
+
+ print STDERR "packed_bytes=$packed_bytes ",
+ "rotate_bytes=$self->{rotate_bytes}\n";
if ($packed_bytes >= $self->{rotate_bytes}) {
$epoch = $max + 1;
} else {
next prev parent reply other threads:[~2019-02-12 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 19:11 V2 shard roll-over Konstantin Ryabitsev
2019-02-12 19:27 ` Eric Wong [this message]
2019-02-27 0:22 ` Eric Wong
2019-02-27 13:26 ` Konstantin Ryabitsev
2019-02-27 20:25 ` [PATCH] v2writable: fix epoch rollover on incremental imports Eric Wong
2019-02-27 23:34 ` Konstantin Ryabitsev
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: http://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=20190212192715.mtncyagjzusi3vtp@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).