unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Is it safe to round-robin the nntp server?
Date: Wed, 1 Sep 2021 16:56:34 -0400	[thread overview]
Message-ID: <20210901205634.guu4p7jyty3ec7qe@meerkat.local> (raw)
In-Reply-To: <20210901205413.GA11375@dcvr>

On Wed, Sep 01, 2021 at 08:54:13PM +0000, Eric Wong wrote:
> > With lore.kernel.org now 3 different nodes with failover, I'm curious if it's
> > safe to point the NNTP server at that as well. I'm assuming that article
> > numbers are going to be the same across all three systems, but I wanted to
> > double-check that it's the case. I.e., if node1 goes down and DNS shifts to
> > point at node2, will that mess up nntp access, or is that okay? What about
> > imap?
> 
> Likely, it depends on how picky NNTP clients are.  The one thing
> that could differ is the "created_at" field in msgmap.sqlite3.
> 
> created_at probably affects IMAP more (UIDVALIDITY), though; and
> I know some IMAP synchronization tools get picky about that.

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.

-K

  reply	other threads:[~2021-09-01 20:56 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 [this message]
2021-09-01 21:03     ` Eric Wong
2021-10-12 12:28       ` 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=20210901205634.guu4p7jyty3ec7qe@meerkat.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).