http://www.slony.info/bugzilla/show_bug.cgi?id=121

           Summary: 'provider node -1 for set' when subscribing from a
                    forwarding node
           Product: Slony-I
           Version: 2.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: low
         Component: slon
        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 has been observed with Slony 2.0.3

I have a 5 node cluster

(1)---->(2)
  \\
   \\
    (3)-----(4)
     \\
      \\
       (5)

With 2 replication sets (origin is node 1), node 3 is a forwarder to nodes 4
and 5.  Node 1 does not communicate directly with 4 or 5.

16:02:55 EDTDEBUG2 remoteWorkerThread_1: Received event #1 from 5000000039
type:ENABLE_SUBSCRIPTION
16:02:55 EDTINFO   copy_set 2 - omit=f - bool=0
16:02:55 EDTINFO   omit is FALSE
16:02:55 EDTERROR  remoteWorkerThread_1: provider node -1 for set 2not found in
runtime configuration
16:02:55 EDTINFO   slon: notify worker process to shutdown
16:02:55 EDTWARN   remoteWorkerThread_1: data copy for set 2 failed 1 times -
sleep 15 seconds
sched_wait_conn: write(): Bad file descriptor
16:02:55 EDTCONFIG slon: child terminated status: 65280; pid: 18487, current
worker pid: 18487
termination of slon2010-05-12 16:02:55 EDTCONFIG slon: child terminated status:
65280; pid: 18487, current worker pid: 18487



The slonik script that generated this set of actions was

cluster name=disorder_replica;
node 1 admin conninfo='dbname=test1 host=localhost user=slony password=test';
define CONNINFO1 'dbname=test1 host=localhost user=slony password=test';
node 2 admin conninfo='dbname=test2 host=localhost user=slony password=test';
define CONNINFO2 'dbname=test2 host=localhost user=slony password=test';
node 3 admin conninfo='dbname=test3 host=localhost user=slony password=test';
define CONNINFO3 'dbname=test3 host=localhost user=slony password=test';
node 4 admin conninfo='dbname=test4 host=localhost user=slony password=test';
define CONNINFO4 'dbname=test4 host=localhost user=slony password=test';
node 5 admin conninfo='dbname=test5 host=localhost user=slony password=test';
define CONNINFO5 'dbname=test5 host=localhost user=slony password=test';
subscribe set(id=2,provider=1,receiver=2,forward=yes);
wait for event(origin=1,confirmed=2,wait on=1);
sync(id=1);
wait for event(origin=1,confirmed=2,wait on=1);
subscribe set(id=2,provider=1,receiver=3,forward=yes);
wait for event(origin=1,confirmed=3,wait on=1);
sync(id=1);
wait for event(origin=1,confirmed=3,wait on=1);
subscribe set(id=2,provider=3,receiver=4);
wait for event(origin=3,confirmed=4,wait on=3);
sync(id=1);
wait for event(origin=3,confirmed=4,wait on=3);
subscribe set(id=2,provider=3,receiver=5);
wait for event(origin=3,confirmed=5,wait on=3);
sync(id=1);
wait for event(origin=3,confirmed=5,wait on=3);


I have seen this error on both nodes 4 and 5 a number of times but I am unable
to reproduce it consistently.  I am not issuing a UNSUBSCRIBE SET, so I think
this is different than bug #111

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