bugzilla-daemon at main.slony.info bugzilla-daemon at main.slony.info
Tue Jan 10 12:21:57 PST 2012
http://www.slony.info/bugzilla/show_bug.cgi?id=260

           Summary: FAILOVER never completes
           Product: Slony-I
           Version: 2.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: slonik
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: ssinger at ca.afilias.info
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


This was reported with slony 2.1.0

Build a cluster with 4 sets all on origin=1.

Node 1 provides this 4 sets to node 2 and node 3.

cluster name=test;
#node 1 admin conninfo='host=localhost dbname=test ';
node 2 admin conninfo='host=localhost dbname=testb ';
node 3 admin conninfo='host=localhost dbname=testc';
failover(id=1, backup node=4);

Never completes, it just keeps waiting for an event.

======================

There are two issues at play here.

1.  While slonik is looping  
for(i=0; i < num_sets; i++)
  it then inside the loop does
   for(i=0; i < num_nodes; i++)

reusing the variable i.


2. failoverset_int() when it runs on node 3 as it gets invoked by slon sets
sl_node.no_active=false and restarts slon.

When slon restarst it does not start the remoteWorkerThread_1 so there is no
thread to process the FAILOVER_SET event for the second set which has
been faked to have ev_origin=1.

-- 
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