[prev in list] [next in list] [prev in thread] [next in thread] 

List:       slony1-general
Subject:    Re: [Slony1-general] Switchover issue.
From:       cbbrowne <cbbrowne () ca ! afilias ! info>
Date:       2009-04-16 15:40:03
Message-ID: 49E75153.70602 () ca ! afilias ! info
[Download RAW message or body]

Nagaraja, Madhukar (Madhukar) wrote:
> Hello,
> 
> I am using slony presently on a 2 node system on a WAN.. One master and other \
> slave. If for somereason the master is not reachable(link down or node down).. Then \
> if I issue a switchover in the slave it will fail bcos it cannot connect to the \
> postgresql on the other side. If I don't want to wait till the other node comes up, \
> then what are the options I have. I did the failover but the process of adding back \
> the failed node to the cluster will not be easy and right now I don't want to use \
> this option. So is there any way I can handle this scenario. 
> Can someone please respond as we have demo coming up shortly ?
> 
> 
You have two choices:

1.  If you have enough connectivity, you can submit MOVE SET.  That does 
require that the origin and subscriber are both available.

2.  If you don't have connectivity, you have to submit FAIL OVER.  That 
does have the serious side-effect of making the ex-origin node 
considered "destroyed."

There isn't a third choice that allows you to do an asynchronous "MOVE 
SET."  And it's not really possible to create such a thing.

-- 
output = ("cbbrowne" "@" "ca.afilias.info")
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"

_______________________________________________
Slony1-general mailing list
Slony1-general@lists.slony.info
http://lists.slony.info/mailman/listinfo/slony1-general


[prev in list] [next in list] [prev in thread] [next in thread]