From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id DA49E1F8C6; Wed, 1 Sep 2021 20:54:13 +0000 (UTC) Date: Wed, 1 Sep 2021 20:54:13 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: Is it safe to round-robin the nntp server? Message-ID: <20210901205413.GA11375@dcvr> References: <20210901203022.lmyudbbouxzt5rfr@meerkat.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210901203022.lmyudbbouxzt5rfr@meerkat.local> List-Id: Konstantin Ryabitsev wrote: > Hello: > > 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.