pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: senthilnathan <senthilnathan.t@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: streaming replication
Date: Tue, 29 Nov 2011 04:08:32 -0800 (PST)
Message-ID: <1322568512313-5032131.post@n5.nabble.com> (raw)
In-Reply-To: <4EB7D6730200002500042B10@gw.wicourts.gov>
References: <CAC-Lqbq7mKzxcNG+cRtUT2vNqh=qY6kXttLeumQkd5vdEsbTVg@mail.gmail.com>
	<CACP4ndiOQZfQ1W5NVNTp0Xvan_RQC+9zQ3=FDe8H1K5szPj+SQ@mail.gmail.com>
	<CAC-Lqbpb5-vETngn-Sc=ab3T=HdWT5GarOpaUjA2O3UuyZ922g@mail.gmail.com>
	<CAHGQGwHn8DLQF1vPaizJzwtFk+Y0ciML-zjXct_y6NmZ+BFy6g@mail.gmail.com>
	<4EB80391.1020809@sesda2.com>
	<4EB7BC8B0200002500042AFF@gw.wicourts.gov>
	<8CC5F53E-1D02-43DE-8198-D2BB9297173E@elevated-dev.com>
	<4EB7C2A30200002500042B0B@gw.wicourts.gov>
	<FBADCDC6-2263-4D99-95A6-9FE98FE078E4@elevated-dev.com>
	<4EB7D6730200002500042B10@gw.wicourts.gov>

Just check the following thread for more details:
http://postgresql.1045698.n5.nabble.com/Timeline-Conflict-td4657611.html

> We have system(Cluster) with Master replicating to 2 stand by servers.
>
> i.e
>
> M   |-------> S1
>
>      |-------> S2
>
> If master failed, we do a trigger file at S1 to take over as master. Now
> we
> need to re-point the standby S2 as slave for the new master (i.e S1)
>
> While trying to start standby S2,there is a conflict in timelines, since
> on
> recovery it generates a new line.
>
> Is there any way to solve this issue?
... [show rest of quote]

Basically you need to take a fresh backup from new master and restart
the standby
using it. But, if S1 and S2 share the archive, S1 is ahead of S2
(i.e., the replay location
of S1 is bigger than or equal to that of S2), and
recovery_target_timeline is set to
'latest' in S2's recovery.conf, you can skip taking a fresh backup
from new master.
In this case, you can re-point S2 as a standby just by changing
primary_conninfo in
S2's recovery.conf and restarting S2. When S2 restarts, S2 reads the
timeline history
file which was created by S1 at failover and adjust its timeline ID to
S1's. So timeline
conflict doesn't happen.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

-- 


--
View this message in context: http://postgresql.1045698.n5.nabble.com/streaming-replication-tp4954954p5032131.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.



view thread (13+ messages)  latest in thread

Message-ID: <1322568512313-5032131.post@n5.nabble.com>
Permalink:  ../1322568512313-5032131.post@n5.nabble.com/
Also on:    postgresql.org/message-id/1322568512313-5032131.post@n5.nabble.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: senthilnathan.t@gmail.com
  Subject: Re: streaming replication
  In-Reply-To: <1322568512313-5032131.post@n5.nabble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox