From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: V2 shard roll-over
Date: Wed, 27 Feb 2019 08:26:04 -0500 [thread overview]
Message-ID: <20190227132604.GA24441@pure.paranoia.local> (raw)
In-Reply-To: <20190227002204.GA17917@dcvr>
On Wed, Feb 27, 2019 at 12:22:04AM +0000, Eric Wong wrote:
> Eric Wong <e@80x24.org> wrote:
> > 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).
>
> Btw, have you checked this? I've been wondering if 7 will show up, too.
Yeah, I've repacked it, but we still haven't rolled over to 7. This is
the latest on the server:
$ git count-objects -v
count: 18
size: 88
in-pack: 1036749
packs: 1
size-pack: 1169104
prune-packable: 0
garbage: 0
size-garbage: 0
$ ls -al objects/pack/pack-7d2041260250f79f5d2396f38959560e013c8d26.pack
-r--r--r--. 1 archiver archiver 1168133236 Feb 27 13:10 objects/pack/pack-7d2041260250f79f5d2396f38959560e013c8d26.pack
I'm looking at the code and I'm not entirely sure what PACKING_FACTOR
is:
my $PACKING_FACTOR = 0.4;
...
rotate_bytes => int((1024 * 1024 * 1024) / $PACKING_FACTOR),
Wouldn't that give us 2.7GB?
(1024*1024*1024)/0.4 = 2,684,354,560
It's possible I'm not following the logic right. It looks to be the same
code that properly sharded things on the initial import, so I'm not
sure.
-K
next prev parent reply other threads:[~2019-02-27 13:26 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
2019-02-27 0:22 ` Eric Wong
2019-02-27 13:26 ` Konstantin Ryabitsev [this message]
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=20190227132604.GA24441@pure.paranoia.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.
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).