<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 9, 2016 at 6:03 PM, Steve Singer <span dir="ltr"><<a href="mailto:steve@ssinger.info" target="_blank">steve@ssinger.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, 9 Oct 2016, Tory M Blue wrote:<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I currently have a setup like this<br>
<br>
Node:<br>
1 primary<br>
2 secondary<br>
3 query <br>
4 query<br>
5 query<br>
11 secondary<br>
12 secondary<br>
13 query<br>
14 query<br>
15 query<br>
<br>
Replication is like this<br>
<br>
Masternode=1<br>
<br>
1 -> 2<br>
2 -> 11 3 4 5<br>
11 -> 12<br>
12 -> 13 14 15<br>
<br>
I'm going to switchover between 1 and 11<br>
<br>
So switchover would mean node 1 becomes secondary and node 11 becomes primary. However as noted above<br>
currently 2 is talking to 11, 1 is not replicating directly to 11 as 2 is doing the wide area replication<br>
to 11..<br>
<br>
So do I have to subscribe 11 to node 1 prior to trying this switchover? How is switchover handled if I<br>
don't , since data in 2 could not be 100% up to date (1000ms delay) when the command is triggered, so 1<br>
would have to finish it's replication to 2 and 2 to 11, before 1 gave the sets to 11?<br>
</blockquote>
<br>
I recommend running move set with a preamble containing admin conninfo to<br>
all your nodes. That way auto wait for can do its thing.<br>
<br>
Most of your questions are answered in<br>
<a href="http://www.slony.info/documentation/2.2/stmtmoveset.html" rel="noreferrer" target="_blank">http://www.slony.info/document<wbr>ation/2.2/stmtmoveset.html</a><br>
<br>
Move set will reverse the subscription chain between 2 and 11, so 11->2<br>
11->1<br>
<br>
If after your move set completes you can make further changes to your<br>
subscription network with<br>
<a href="http://www.slony.info/documentation/2.2/stmtresubscribenode.html" rel="noreferrer" target="_blank">http://www.slony.info/document<wbr>ation/2.2/stmtresubscribenode.<wbr>html</a><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Also when I tear down the primary site (completely) how do I move, promote, migrate the masternode (right<br>
now the config sees the masternode as 1, but when I drop 1-5 at some point from 11/12, I don't have a<br>
masternode 1 anymore, so how do I configure the system to treat 11 as masternode?<br>
</blockquote>
<br>
Once your move set completes node 11 is your master node(for those tables) that is exactly what move set does, it makes node 11 the origin(master).<br>
<br>
Slony does not support renaming node, don't try to make some other node in the cluster be renamed to node 1 after this.<br>
<br>
I encourage you to setup a test/staging cluster in your configuration and try various scenarios out before executing the commands on your production cluster.<br>
<br>
Steve<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks<br>
Tory<br>
<br>
<br></blockquote></blockquote><div><br></div><div>Thanks Steve,</div><div><br></div><div>i've done all this quite a few times, switchovers and moving sets. But I was not 100% sure if I could just go from 1-11 when 2 was replicating to 11. Earlier today I went a head and did some moving so that 1 is replicating to 11, so the switchover will be as clean as moving sets to 11 and 1 will become the secondary, just to make sure I didn't introduce any weirdness.</div><div><br></div><div>And thanks for the heads up on the masternode. I would never try to rename anything inside the cluster, but since our scripts all require a masternode switch, I was not 100% sure that the masternode was in fact just the primary db at that time </div><div><br></div><div>Thanks again for taking the time!!</div><div><br></div><div>Tory</div></div><br></div></div>