From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Is it safe to round-robin the nntp server?
Date: Tue, 12 Oct 2021 12:28:02 +0000 [thread overview]
Message-ID: <20211012122802.M615085@dcvr> (raw)
In-Reply-To: <20210901210342.GB11375@dcvr>
Eric Wong <e@80x24.org> wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > On Wed, Sep 01, 2021 at 08:54:13PM +0000, Eric Wong wrote:
> > > Likely, it depends on how picky NNTP clients are. The one thing
> > > that could differ is the "created_at" field in msgmap.sqlite3.
> >
> > Is that value taken from git repos, or generated during indexing? All 3 nodes
> > replicating from the same set of sources, but they do indeed run the index
> > hooks at slightly different times.
>
> Whenever public-inbox-init runs for v2 (first public-inbox-index for v1).
Fwiw, it should be possible to automate ->created_at
synchronization using Last-Modified from /_/text/config/raw.
"lei add-external --mirror" or public-inbox-clone +index will
both set ->created_at automatically to match Last-Modified of
the origin:
https://public-inbox.org/meta/20211012114705.383-10-e@80x24.org/
([PATCH 9/9] www: _/text/config/raw Last-Modified: is mm->created_at)
prev parent reply other threads:[~2021-10-12 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 20:30 Is it safe to round-robin the nntp server? Konstantin Ryabitsev
2021-09-01 20:54 ` Eric Wong
2021-09-01 20:56 ` Konstantin Ryabitsev
2021-09-01 21:03 ` Eric Wong
2021-10-12 12:28 ` Eric Wong [this message]
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=20211012122802.M615085@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.
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).