Hello slony community,
                I’m working now on some slony1 failover automation (slony1-2.2.4) and I’m having a lot of trouble getting slony1 to honor MOVE SET commands. Below are the commands I’m using, to my mind pretty simple instructions to move a set and confirm everyone gets the message (wait for event, confirmed by all) before moving on. Shortly after moving on, I’m dropping the former set origin node. I suspect that’s why one of subscribers enters the perpetual “MOVE_SET not received yet” loop, which I know isn’t a new slony1 problem. Is there any reason this shouldn’t work? The FAILOVER command never does this. In the scenario I’m working on, I would have liked to avoid the heavy hammer, but do I need to use FAILOVER to make this happen reliably?
                Thanks in advance,


--- slonik commands ----
lock set (id=1, origin=1);
move set (id=1, old origin=1, new origin=3);
wait for event (origin=3, confirmed=all,
                        wait on=3, timeout=60);
----

---- remote subscriber log ----
2016-06-28 12:23:26 UTC [19800] INFO   start processing ACCEPT_SET
2016-06-28 12:23:26 UTC [19800] INFO   ACCEPT: set=1
2016-06-28 12:23:26 UTC [19800] INFO   ACCEPT: old origin=1
2016-06-28 12:23:26 UTC [19800] INFO   ACCEPT: new origin=3
2016-06-28 12:23:26 UTC [19800] INFO   ACCEPT: move set seq=5000000008
2016-06-28 12:23:26 UTC [19800] INFO   got parms ACCEPT_SET
2016-06-28 12:23:26 UTC [19800] INFO   ACCEPT_SET - MOVE_SET not received yet - sleep
2016-06-28 12:23:36 UTC [19800] INFO   ACCEPT_SET - MOVE_SET not received yet - sleep
2016-06-28 12:23:46 UTC [19800] INFO   ACCEPT_SET - MOVE_SET not received yet - sleep
2016-06-28 12:23:56 UTC [19800] INFO   ACCEPT_SET - MOVE_SET not received yet - sleep
2016-06-28 12:24:06 UTC [19800] INFO   ACCEPT_SET - MOVE_SET not received yet - sleep
2016-06-28 12:24:16 UTC [19800] INFO   ACCEPT_SET - MOVE_SET not received yet – sleep
----


                Tom    ☺


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20160628/72cd8eef/attachment.htm