Tue Jun 21 06:00:22 PDT 2011
- Previous message: [Slony1-bugs] [Bug 222] cleanup thread can lock out new application connections
- Next message: [Slony1-bugs] [Bug 216] monitor threads don't work on Win32
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=223 Summary: slonik can wait for a node it just uninstalled Product: Slony-I Version: devel 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 Create a slonik cluster with a few nodes (say 1,2,3). The perform an uninstall node on 1 and 2. Start slonik back up and init cluster(id=1); and store node(id=2); Start slonik up again. uninstall node(id=3); subscribe set(id=1, provider=1,receiver=3); slonik will print stuff like: 'waiting for events (3,5000000077) only at (3,0) to be confirmed on node 1' When slonik sees an uninstall node it needs to erase the remembered 'last event' from that node. This was observed with 2.1.0 beta 2 -- 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.
- Previous message: [Slony1-bugs] [Bug 222] cleanup thread can lock out new application connections
- Next message: [Slony1-bugs] [Bug 216] monitor threads don't work on Win32
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list