From: | Santhosh Kumar <krssanthosh(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Behaviour of failed Primary |
Date: | 2020-05-21 05:03:14 |
Message-ID: | CANCPq3g-2bpoukLyHpM3txrNusfjFwow6Q5sL3qXVdPD+CwmUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Hi Forum,
If I have a cluster with Synchronous replication enabled with three nodes,
for eg:
[primary] [hot stand by 1] [host stand by 2]
And for some unforeseen reasons, if primary fails, the failover will kick
in and hot stand by 1 will become new primary and cluster setup will look
like this
[new primary (hot stand by1)] [host stand by 2]
My question here is, what will happen if the original primary which has
failed comes back. Will it become part of this high available replica
cluster automatically or it will be stale and disconnected from the
cluster?
How can we automatically make the failed primary to be part of the
cluster with hot standby role? It would be of great help, if you can direct
me to any references details. Thank you, upfront.
Regards,
Santhosh
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2020-05-21 05:09:25 | Re: How to recover from compressed wal archieve in windows |
Previous Message | Paul Förster | 2020-05-21 04:55:41 | Re: How to recover from compressed wal archieve in windows |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-05-21 05:06:18 | Re: Parallel Seq Scan vs kernel read ahead |
Previous Message | John Naylor | 2020-05-21 04:12:13 | Re: PostgreSQL 13 Beta 1 Release Announcement Draft |