Tue Dec 7 12:12:06 PST 2010
- Previous message: [Slony1-bugs] [Bug 177] New: Refactor logshipping code out of slon
- Next message: [Slony1-bugs] [Bug 178] More sophisticated FAILOVER
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=178 Summary: More sophisticated FAILOVER 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: cbbrowne at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 General proposal, that FAILOVER be a much more sophisticated command, allowing: * Dropping nodes considered dead * Doing several failovers of sets as one request Thus, something like: <pre> failover (dead nodes=(1,2,4), set id=1, backup node=3, set id=2, backup node=5, set id=3, backup node=3); </pre> * Failover should check various conditions and abort if any are the case ** There need to be paths to support communications to let the new masters catch up ** Slons need to be running for nodes that are needed to let masters catch up ** If a node hosts a subscription that cannot be kept that subscription may be marked dead *** Automatically kill that subscription? *** Refuse failover until subscription is marked dead? This requires a dead subscription clause be added... -- 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 177] New: Refactor logshipping code out of slon
- Next message: [Slony1-bugs] [Bug 178] More sophisticated FAILOVER
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list