Sorry for late on this, its due to actual Production swap implementation.
Though I tested as suggested, I didnt get time to post my reply.
After doing vigorous testing by taking into consideration Steve Jan
points, we succeded it without any problem.
This analysis is flawed. The two event
Using streaming replication for the DR Master could present a problem.
Since it is in the same data center the following may seem unlikely. But
what can happen is that the DR Master is further behind in replication than
the Slony Slave at the moment, disaster strikes and the Master becomes
On 6/25/2012 3:36 AM, Raghav wrote:
Using streaming replication for the DR Master could present a
problem. Since it is in the same data center the following may seem
unlikely. But what can happen is that the DR Master is further
behind in replication than the Slony Slave at
This analysis is flawed. The two event numbers are from different origins
and therefore, don't compare to each other. The combination of
ev_origin,ev_seqno can never be higher on any node, than it is on the
origin itself.
Thanks Jan. For correcting me, let me recheck thoroughly from my side
Also, one more point on step 3, there cannot be any DML's until this
operation is done successfully, because, in step 2 you are stopping SR and
doing DML's on Step 3, which is clearly know fact that your DR-master dont
have any effect made in Step 3.
--Raghav
On 6/21/2012 11:27 PM, Raghav wrote:
Q: What I want to achieve ?
A: Swap the Masters. Means, now slave should receive events from
DR-Master once it get promoted to Master as shown below
Have you read 'Controlled Switchover'
On 12-06-21 11:27 PM, Raghav wrote:
Thank you Steve. Make sense to me.
Sorry to say, my question was how to avoid resubscribing DR-Master to
slave and then promoting it to master. Since, complete information of
master is available on dr-master.
Due to my curiosity level :) I tested again
You can use the built-in streaming replication for what you describe but
if you want unplanned failover it should be the SYNCHRONOUS replication.
asynchronous replication will work fine for a controlled switchover (stop
the slons, let your 'DR Master' get caught up with streaming
On 12-06-20 12:28 PM, Raghav wrote:
Hi Steve,
Below is the scenario I want to achieve.
Warm-Standby
Master DR-Master
|
|Replication built on Slony 2.1.
|
V
Slave
Given is actually setup
Q: What I want to achieve ?
A: Swap the Masters. Means, now slave should receive events from
DR-Master once it get promoted to Master as shown below
Have you read 'Controlled Switchover' http://www.slony.info/**
Hi Steve,
Below is the scenario I want to achieve.
Warm-Standby
Master DR-Master
|
|Replication built on Slony 2.1.
|
V
Slave
Given is actually setup of production, master/slave replication with log
11 matches
Mail list logo
