From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Dylan Luong <Dylan(dot)Luong(at)unisa(dot)edu(dot)au> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Resync second slave to new master |
Date: | 2018-03-06 05:23:41 |
Message-ID: | 20180306052341.GA4717@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Mar 06, 2018 at 04:45:10AM +0000, Dylan Luong wrote:
> After a failover (promote) to the Slave1, is it easily resync the
> Slave2 to the new master (old slave1)? Do we need to do full rebuild
> of the Slave2 from new master everytime we failover to Slave1 from
> Master? Can we use pg_rewind on Slave2 to resyn it with new master
> (old slave1)?
After promoting slave 1, it could be possible that some records have
slipped to slave 2 from the primary. In this case, a rewind would be
recommended. You should be careful that your slave 2 has not received
WAL to a position newer than where WAL has forked because of the
promotion. If that happened, then a rewind would be necessary before
replugging slave 2 to the newly-promoted server. Be very careful with
your failover flow here. pg_rewind also would not run if it finds that
the target server does not need a rewind, so you could stop the slave 2,
and run pg_rewind unconditionally to keep things simple.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Dylan Luong | 2018-03-06 06:00:40 | RE: Resync second slave to new master |
Previous Message | Adrian Klaver | 2018-03-06 05:13:08 | Re: org.postgresql.util.PSQLException: Error could not open file "base/": No such file or directory |