From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Rob Emery <re-pgsql(at)codeweavers(dot)net> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Replication: re-initialisation of failed master |
Date: | 2015-03-03 20:57:34 |
Message-ID: | CAECtzeUAiKi9hW2GXUi=i5+wzPXYipnDh0OJxQtSG+kiLX53VQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hey,
2015-03-03 20:59 GMT+01:00 Rob Emery <re-pgsql(at)codeweavers(dot)net>:
> Hello all,
>
> We run a 2 node setup replicating between a master and synchronous slave,
> currently when we want to failover we basically kill the master off, create
> a recovery file and re-point the traffic via a DNS record etc, we're
> looking at implementing a corosync/pacemaker setup shortly.
>
> Once we're running with the old secondary as the master the only way we
> have to re-stage the old master is to use pg_basebackup against the new
> master to replace the previous master's data directory.
>
> It feels that given how little has probably changed on the new master
> versus the old master that there should be a faster way of re-initializing
> the old master as a slave. Is there some sort of short-cut speedup I'm
> missing here? I suppose I'm mainly curious as to what techniques most
> admins use to accomplish this!
>
>
rsync is the usual answer to this kind of issues.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Borodin | 2015-03-04 06:16:13 | Re: Replication: re-initialisation of failed master |
Previous Message | Rob Emery | 2015-03-03 19:59:43 | Replication: re-initialisation of failed master |