From: | Vladimir Borodin <root(at)simply(dot)name> |
---|---|
To: | Robert Emery <robertemery(at)codeweavers(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Replication: re-initialisation of failed master |
Date: | 2015-03-04 08:34:40 |
Message-ID: | CFF7C505-1C80-4712-9EB8-2BBD0320F039@simply.name |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> 4 марта 2015 г., в 11:23, Robert Emery <robertemery(at)codeweavers(dot)net> написал(а):
>
> That looks like a really cool tool, I've not seen that before!
>
> Have you used that yourself in a real scenario?
Yes, I do use it for 9.3 and 9.4 in production about a couple of times a month.
>
> On 4 March 2015 at 06:16, Vladimir Borodin <root(at)simply(dot)name <mailto:root(at)simply(dot)name>> wrote:
> Hi.
>
>> 3 марта 2015 г., в 22:59, Rob Emery <re-pgsql(at)codeweavers(dot)net <mailto: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!
>
> https://github.com/vmware/pg_rewind <https://github.com/vmware/pg_rewind> is the solution for your problem.
>
>>
>> Thanks in advance
>> Rob
>>
>>
>> <http://www.codeweavers.net/>
>>
>>
>> March Newsletter - Customers want a high quality ‘clicks & bricks’ F & I experience <http://us6.campaign-archive2.com/?u=db934935d4174e46e9063c8c4&id=2578f201d7&e=[UNIQID]>
>>
>> Last Month Product Highlights <https://www.codeweavers.net/company-blog/february-product-highlights>
>>
>> Codeweavers Ltd | Barn 4 | Dunston Business Village | Dunston | ST18 9AB
>> Registered in England and Wales No. 04092394 | VAT registration no. 974 9705 63
>>
>> <https://twitter.com/CodeweaversTeam>
>> <http://www.codeweavers.net/>
>> <mailto:contactus(at)codeweavers(dot)net>
>> <http://www.linkedin.com/company/225698?trk=tyah>
>> <https://www.facebook.com/codeweaverssoftware>
>
> --
> May the force be with you…
> https://simply.name <https://simply.name/>
>
>
>
> --
> Robert Emery
> Head of Infrastructure
>
> E: robertemery(at)codeweavers(dot)net <mailto:robertemery(at)codeweavers(dot)net> | T: 01785 711633 | W: www.codeweavers.net <http://www.codeweavers.net/>
>
> <http://www.codeweavers.net/>
>
>
> March Newsletter - Customers want a high quality ‘clicks & bricks’ F & I experience <http://us6.campaign-archive2.com/?u=db934935d4174e46e9063c8c4&id=2578f201d7&e=[UNIQID]>
>
> Last Month Product Highlights <https://www.codeweavers.net/company-blog/february-product-highlights>
>
> Codeweavers Ltd | Barn 4 | Dunston Business Village | Dunston | ST18 9AB
> Registered in England and Wales No. 04092394 | VAT registration no. 974 9705 63
>
> <https://twitter.com/CodeweaversTeam>
> <http://www.codeweavers.net/>
> <mailto:contactus(at)codeweavers(dot)net>
> <http://www.linkedin.com/company/225698?trk=tyah>
> <https://www.facebook.com/codeweaverssoftware>
--
May the force be with you…
https://simply.name
From | Date | Subject | |
---|---|---|---|
Next Message | Ville Rantamaula | 2015-03-04 11:01:32 | Re: PostgreSQL with BDR. Problems when adding a sequence in a table column |
Previous Message | Vladimir Borodin | 2015-03-04 06:16:13 | Re: Replication: re-initialisation of failed master |