From: | Azimuddin Mohammed <azimeiu(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Postgres HA |
Date: | 2018-01-05 19:07:10 |
Message-ID: | CAKUuFd7x8FAg0V8+mStBeXcctpbykTz5uf0J0dtdEgfW9DL3Hg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Hello,
I am little confused with how HA works in postgres. Reading the article
which state as below "*If the primary server fails and the standby server
becomes the new primary, and then the old primary restarts, you must have a
mechanism for informing the old primary that it is no longer the primary.
This is sometimes known as STONITH (Shoot The Other Node In The Head),
which is necessary to avoid situations where both systems think they are
the primary, which will lead to confusion and ultimately data loss.*
*Many failover systems use just two systems, the primary and the standby,
connected by some kind of heartbeat mechanism to continually verify the
connectivity between the two and the viability of the primary. It is also
possible to use a third system (called a witness server) to prevent some
cases of inappropriate failover, but the additional complexity might not be
worthwhile unless it is set up with sufficient care and rigorous testing.*
*PostgreSQL does not provide the system software required to identify a
failure on the primary and notify the standby database server. Many such
tools exist and are well integrated with the operating system facilities
required for successful failover, such as IP address migration."*
Can someone explain how the HA failback will take place and what open
source tools we can use to make sure once the primary server which failed
over to slave will mark itself as slave.
Appreciate your response in advance.
--
Regards,
Azim
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
From | Date | Subject | |
---|---|---|---|
Next Message | Jerry Sievers | 2018-01-05 19:12:37 | Re: pg_rewind: confused about recovery.conf/restore_command |
Previous Message | Rui DeSousa | 2018-01-05 14:55:40 | Re: pg_rewind: confused about recovery.conf/restore_command |
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2018-01-05 19:18:56 | Re: Postgres HA |
Previous Message | Adrian Klaver | 2018-01-05 18:24:57 | Re: What generates pg_config.h? |