user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <>
Subject: Is it safe to round-robin the nntp server?
Date: Wed, 1 Sep 2021 16:30:22 -0400	[thread overview]
Message-ID: <20210901203022.lmyudbbouxzt5rfr@meerkat.local> (raw)


With 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


             reply	other threads:[~2021-09-01 20:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 20:30 Konstantin Ryabitsev [this message]
2021-09-01 20:54 ` Is it safe to round-robin the nntp server? Eric Wong
2021-09-01 20:56   ` Konstantin Ryabitsev
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210901203022.lmyudbbouxzt5rfr@meerkat.local \ \ \

* 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

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).