Re: Streaming replication, master recycling

From: Venkata Balaji N <nag1010(at)gmail(dot)com>
To: fredrik(at)huitfeldt(dot)com
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Streaming replication, master recycling
Date: 2016-05-11 10:47:13
Message-ID: CAEyp7J-P+E1i24g6TnDNj=ib9yENS+XP-pTs2v3aNM-TmSjodQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, May 11, 2016 at 2:31 PM, <fredrik(at)huitfeldt(dot)com> wrote:

> Hi All,
>
> we are currently using streaming replication on multiple node pairs. We
> are seeing some issues, but I am mainly interrested in clarification.
>
> When a failover occurs, we touch the trigger file, promoting the previous
> slave to master. That works perfectly.
>
> For recycling the previous master, we create a recovery.conf (with
> recovery_target_timeline = 'latest') and *try* to start up. If postgresql
> starts up, we accept it as a new slave. If it does not, we proceed with a
> full basebackup.
>

Which version of postgresql you are using ?

You need to shutdown master first, then promote slave and then other way
round, but, this can be clarified only if you let us know the postgresql
version. This is quite tricky in 9.2.x and from 9.3.x.

Regards,
Venkata B N

Fujitsu Australia

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message fredrik 2016-05-11 11:04:19 Re: Streaming replication, master recycling
Previous Message martin.kamp.jensen 2016-05-11 10:44:03 Re: Invalid data read from synchronously replicated hot standby