From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id D5A571F453;
	Tue, 12 Feb 2019 19:27:15 +0000 (UTC)
Date: Tue, 12 Feb 2019 19:27:15 +0000
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: V2 shard roll-over
Message-ID: <20190212192715.mtncyagjzusi3vtp@dcvr>
References: <20190212191116.GA8720@chatter.qube.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20190212191116.GA8720@chatter.qube.local>
List-Id: <meta.public-inbox.org>

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 {