I mistyped and yes B101 is a replica node, not primary.
The correct architecture is
A101(primary) -> A201(replica) -> B101(replica) -> B201(replica)
On Mon, Oct 3, 2022 at 5:55 PM Michael Paquier wrote:
> On Mon, Oct 03, 2022 at 12:41:23PM -0700, John Bolliger wrote:
> > Our architecture is sim
On Mon, Oct 03, 2022 at 12:41:23PM -0700, John Bolliger wrote:
> Our architecture is similar but all of the servers are now on ZFS now and
> Postgres 13.8 with Ubuntu 18.04+ and still doing streaming replication, all
> with ECC memory and 26-64 cores with 192gb ram+ on top of a ZPOOL made out
> of
On Fri, Jun 29, 2018 at 1:14 PM, Devin Christensen wrote:
>> From your description it sounds like it's happening in the middle of
>> streaming, right?
>
> Correct. None of the instances in the chain experience a crash. Most of the
> time I see the "incorrect resource manager data checksum in recor
> From your description it sounds like it's happening in the middle of
streaming, right?
Correct. None of the instances in the chain experience a crash. Most of the
time I see the "incorrect resource manager data checksum in record" error,
but I've also seen it manifested as:
invalid magic number
On Fri, Jun 29, 2018 at 5:44 AM, Devin Christensen
wrote:
> The pattern is the same, regardless of ubuntu or postgresql versions. I'm
> concerned this is somehow a ZFS corruption bug, because the error always
> occurs downstream of the first ZFS node and ZFS is a recent addition. I
> don't know en
