From: Hammerman, Joseph <JosephHammerman@iheartmedia.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Failover with a tertiary read-only secondary
Date: Fri, 31 Mar 2017 16:24:58 +0000
Message-ID: <D503FB0C.6C95%JosephHammerman@iheartmedia.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Hi Postgres Admin users list,
We have a PostgreSQL 93 master instance. We have a secondary set up as a hot streaming replica. There is a third machine that is a read only slave copying from a CNAME service DNS record. If the primary is demoted and the secondary is promoted and the CNAME redirected to the secondary, the read only slave will not pick up replication. The error messages in the log are:
2017-03-31 11:08:03 EDT [31062]: [799-1] ( - ) LOG: restarted WAL streaming at 0/9000000 on timeline 1
2017-03-31 11:08:03 EDT [31062]: [800-1] ( - ) LOG: replication terminated by primary server
2017-03-31 11:08:03 EDT [31062]: [801-1] ( - ) DETAIL: End of WAL reached on timeline 1 at 0/9000090
I believe that these messages are being generated because the WAL checkpoints on the promoted secondary are not the same as they were on demoted primary. Is there a method to remediate this? Or do I need to perform a full resync to both the readonly secondary and the demoted primary?
Thanks in advance for any assistance anyone can provide,
Joseph Hammerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: JosephHammerman@iheartmedia.com
Subject: Re: Failover with a tertiary read-only secondary
In-Reply-To: <D503FB0C.6C95%JosephHammerman@iheartmedia.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox