slony1-bugs at lists.slony.info slony1-bugs at lists.slony.info
Tue Apr 7 03:08:20 PDT 2009
http://www.slony.info/bugzilla/show_bug.cgi?id=80

           Summary: slon daemon restarts itself in a loop after failover()
           Product: Slony-I
           Version: 1.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: core scripts
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: pfote at ypsilon.net
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


Created an attachment (id=31)
 --> (http://www.slony.info/bugzilla/attachment.cgi?id=31)
log and slonik scripts

when dropping the "failed" node immediately after the failover() command, it
might happen that a node gets the dropNode_int() command while the failed node
is still referenced in the sl_set table. the dropNode_int() then fails because
the foreign key contraint "set_origin-no_id-ref" fails. 
The slon deamon then restarts itself and tries again to drop the node (which
fails) and restarts itself in a endless loop, rendering the node unusable;

If you wait a bit after the failover() before dropping the node, everything
works fine.

attached are the slonik scripts to setup the test and to (hopefully) reproduce
the problem, and some of the slon daemon log of the node that went wild.

The setup was as follow: 4 nodes 1-4, 1 as master, 2-4 as slaves directly
subscribing on the master. then the master is assumed to be broken and 4 should
become the new master, so nodes 2 and 3 are re-subscribed to node 4, then the
failover is executed, waited and then the "failed" old master dropped.

i have to apologize i forgot to switch languages on me dev machine so some of
the error messages in the slon log are in german.

Cheers
Andreas


-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Slony1-bugs mailing list