From: Hammerman, Joseph <JosephHammerman@iheartmedia.com>
To: bricklen <bricklen@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Failover with a tertiary read-only secondary
Date: Fri, 31 Mar 2017 18:35:06 +0000
Message-ID: <D5041934.6CA6%JosephHammerman@iheartmedia.com> (raw)
In-Reply-To: <CAGrpgQ8cbQJc3iFq2KQ2dA5O76-r3t_EB1MiApY2oNRt6UYnRg@mail.gmail.com>
References: <D503FB0C.6C95%JosephHammerman@iheartmedia.com>
<CAGrpgQ8cbQJc3iFq2KQ2dA5O76-r3t_EB1MiApY2oNRt6UYnRg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Hi bricklen,
Thanks for the assistance! To answer your questions,
1. Yes, the behavior persisted following a restart.
2. Not a bad idea, but that only delays the necessity of a resync until the next failover…. Unless I’m missing something?
Thanks,
Joseph Hammerman
From: bricklen <bricklen@gmail.com<mailto:bricklen@gmail.com>>
Date: Friday, March 31, 2017 at 2:31 PM
To: Joseph Hammerman <JosephHammerman@iheartmedia.com<mailto:JosephHammerman@iheartmedia.com>>
Cc: "pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>" <pgsql-admin@postgresql.org<mailto:pgsql-admin@postgresql.org>>
Subject: Re: [ADMIN] Failover with a tertiary read-only secondary
On Fri, Mar 31, 2017 at 9:24 AM, Hammerman, Joseph <JosephHammerman@iheartmedia.com<mailto:JosephHammerman@iheartmedia.com>> wrote:
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
Two questions:
1). After the DNS change, did you restart the downstream replica? (after the upstream was promoted)
2). You might be able to sidestep the issue if you set up cascading replicas, as in the first replica is streaming from the master, and the second replica is streaming from the upstream replica.
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, bricklen@gmail.com
Subject: Re: Failover with a tertiary read-only secondary
In-Reply-To: <D5041934.6CA6%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