Bug 123 - Adding a node shortly after deleting it causes 'node -1 not found'
Summary: Adding a node shortly after deleting it causes 'node -1 not found'
Status: NEW
Alias: None
Product: Slony-I
Classification: Unclassified
Component: slon (show other bugs)
Version: 2.0
Hardware: All All
: medium major
Assignee: Slony Bugs List
URL:
Depends on:
Blocks:
 
Reported: 2010-05-17 07:07 UTC by Steve Singer
Modified: 2010-06-18 10:35 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Singer 2010-05-17 07:07:43 UTC 
This test was performed on a 5 node cluster  with 2.0.x (CVS)
 
1=====>2
\\
 \\
  3=====>5
   \\
    4

A subscription set was subscribed to all nodes.

Then 
-The slon for node 4 was killed
-Node 4 was dropped from replication, with node 1 being the event node
-A 'store node(id=4,event node=3) was executed  + add paths
-The slon for node 4 was started
-Node 4 is subscribed to the set coming from node 3.


The slon for node 4 encounters

Received event #1 from 5000000049 type:ENABLE_SUBSCRIPTION
2010-05-17 09:41:51 EDTINFO   copy_set 1 - omit=f - bool=0
2010-05-17 09:41:51 EDTINFO   omit is FALSE
2010-05-17 09:41:51 EDTERROR  remoteWorkerThread_1: provider node -1 for set 1not found in runtime configuration


The sl_event table on node 4 contains


4 5000000001  STORE_PATH
1 5000000048  SYNC
5 5000000004  SYNC
3 5000000011  STORE_NODE
3 5000000012  ENABLE_NODE
3 5000000013  STORE_PATH
3 5000000014  SUBSCRIBE_SET (3,4)
3 5000000015  SYNC
4 5000000002  SYNC
1 5000000049  ENABLE_SUBSCRIPTION  (3,4)

Slon seems to be processing the ENABLE_SUBSCRIPTION that is marked as having an ev_origin of node 1 (the set origin) before the SUBSCRIBE_SET (having an ev_origin of node 3, the provider)