From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Troubleshooting threads missing from /all/
Date: Sun, 17 Oct 2021 14:04:50 -0400 [thread overview]
Message-ID: <20211017180450.e6zsbbx2at2rggxx@nitro.local> (raw)
In-Reply-To: <20211016094324.GA16488@dcvr>
On Sat, Oct 16, 2021 at 09:43:24AM +0000, Eric Wong wrote:
> Eric Wong <e@80x24.org> wrote:
> > Yes. Though given the current situation with missing messages
> > from /all/, I'd wait until a reindex recovers the missing
> > messages (and probably a fast fsck checker).
>
> I think "public-inbox-extindex --reindex --all --fast" is
> reasonably ready as an fsck checker. I've been running it a
> bunch in recent days/weeks and also found+fixed some other bugs
> along the way.
Thanks, Eric! I've been out this week for some family time (it was
Thanksgiving in Canada), which is why I was staying conspicuously silent. :)
I'll give --reindex --fast a whirl in the next few days.
> With --fast, --reindex takes around 20 minutes for me with
> "--batch-size=20m --no-fsync". The first run may take longer
> if it has stuff to do. But running it repeatedly should not
> cause it to complain about unseen/stale/mismatched messages
> (likely the first run will).
>
> So it's not /really/ fast, but compared to ~35 hours w/o --fast,
> then it's alright. Either way, --reindex should be safe
> with parallel -index and -extindex being run by cronjobs.
Absolutely, thanks for working on this.
-K
next prev parent reply other threads:[~2021-10-17 18:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 13:05 Troubleshooting threads missing from /all/ Konstantin Ryabitsev
2021-10-01 19:58 ` Eric Wong
2021-10-01 20:08 ` Konstantin Ryabitsev
2021-10-01 20:41 ` Eric Wong
2021-10-01 20:49 ` Konstantin Ryabitsev
2021-10-01 20:54 ` Eric Wong
2021-10-01 20:58 ` Konstantin Ryabitsev
2021-10-01 22:25 ` Eric Wong
2021-10-01 22:27 ` Eric Wong
2021-10-01 23:11 ` Konstantin Ryabitsev
2021-10-01 23:46 ` Eric Wong
2021-10-02 0:02 ` Eric Wong
2021-10-05 4:39 ` Eric Wong
2021-10-05 18:03 ` Konstantin Ryabitsev
2021-10-06 10:18 ` Eric Wong
2021-10-07 8:36 ` Eric Wong
2021-10-07 13:57 ` Konstantin Ryabitsev
2021-10-07 21:36 ` Eric Wong
2021-10-07 21:33 ` Eric Wong
2021-10-07 21:33 ` Eric Wong
2021-10-08 17:33 ` Konstantin Ryabitsev
2021-10-08 21:34 ` Eric Wong
2021-10-16 9:43 ` Eric Wong
2021-10-17 18:04 ` Konstantin Ryabitsev [this message]
2021-10-17 23:12 ` Eric Wong
2021-10-18 5:25 ` Eric Wong
2021-10-18 14:04 ` Konstantin Ryabitsev
2021-10-18 14:03 ` Konstantin Ryabitsev
2021-10-24 0:03 ` Eric Wong
2021-10-26 21:11 ` Konstantin Ryabitsev
2021-10-29 10:18 ` release updates [was: Troubleshooting threads missing from /all/] Eric Wong
2021-10-01 20:17 ` Troubleshooting threads missing from /all/ Konstantin Ryabitsev
2021-10-02 11:39 ` 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=20211017180450.e6zsbbx2at2rggxx@nitro.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).