unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: Eric Wong <e@80x24.org>
Cc: "Robin H. Johnson" <robbat2@gentoo.org>,
	meta@public-inbox.org, infra@gentoo.org
Subject: Re: public-inbox skipping new inboxes or many mails
Date: Wed, 17 Jul 2024 03:04:33 +0000	[thread overview]
Message-ID: <robbat2-20240717T025915-124684207Z@orbis-terrarum.net> (raw)
In-Reply-To: <20240716190550.M242334@dcvr>

[-- Attachment #1: Type: text/plain, Size: 2538 bytes --]

On Tue, Jul 16, 2024 at 07:05:50PM +0000, Eric Wong wrote:
> > It's definitely very busy after scan, but I can't tell if it's the full
> > set.
> OK, I think adding stderr diagnostic messages for full scans
> shouldn't be too noisy.
Thanks. I think it will be needed...

> > At an admin level, is there a way to dump out all of the paths it's
> > indexes, to compare against the paths on disk?
> No, path information isn't stored for public-facing inboxes
> since it's too unstable.  It should be possible to reverse map
> things at real-time and add better diagnostic tools, but the
> philosophy has always been to store||index as little as possible
> and be able to infer/regenerate needed data on-the-fly to avoid
> data consistency problems.
Can I easily dump out every message-id at least? I can compare that
against the files, other than the old messages with no message-ids.

> > > How many Maildirs are you watching?  I wonder if it's hitting
> > > RLIMIT_NOFILE... (errors should be logged to stderr).
> > 6774 Maildirs right now.
> > I should probably improve the OpenRC script for it, I think we're
> > throwing away stderr right now for -watch.
> 
> Yeah, watch stderr is important for diagnosing problems.
> 
> Fwiw, I run it inside a screen(1) session on one system,
> and rely on systemd to redirect stderr to syslog on another
I hacked in stderr: but bad luck, it doesn't dump anything useful before
it seems to vanish. Nothing in dmesg either, so a mundane crash.

> > > Curious, which architecture is that and is it using
> > > Linux::Inotify2 or inotify via the `syscall' perlop?
> > > (I expect 3 is the inotify FD).
> > x86-64, dev-perl/Linux-Inotify2 is installed on the host, but I can't
> > tell at a glance if -watch used perlop or package.
> 
> Probably, yes; but it can/should favor the pure Perl version
> soon.  Since it's Gentoo I trust it's up-to-date with broadcast
> and overflow support?
dev-perl/Linux-Inotify2 will be up to date. No guarantees that the
kernel is up to date - some legacy boxes at sponsors are pretty crufty
and have been unsafe to reboot to new kernels when we lack any OOB
management access: to that end, public-inbox's responsiveness is amazing
even running on a 10+ year old RAID1 HDD spinner setup.

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation President & Treasurer
E-Mail   : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]

  reply	other threads:[~2024-07-17  3:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15  6:15 public-inbox skipping new inboxes or many mails Robin H. Johnson
2024-07-15 21:03 ` Eric Wong
2024-07-15 21:45   ` Robin H. Johnson
2024-07-15 23:58     ` Eric Wong
2024-07-16  5:45       ` Robin H. Johnson
2024-07-16 19:05         ` Eric Wong
2024-07-17  3:04           ` Robin H. Johnson [this message]
2024-07-17 23:25             ` Eric Wong
2024-07-17 23:50               ` Eric Wong
2024-07-18  0:02               ` Robin H. Johnson

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=robbat2-20240717T025915-124684207Z@orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=e@80x24.org \
    --cc=infra@gentoo.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).