Thu Dec 16 08:54:45 PST 2010
- Previous message: [Slony1-bugs] [Bug 171] Health Check: Verify node's parentage
- Next message: [Slony1-bugs] [Bug 171] Health Check: Verify node's parentage
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=171 Christopher Browne <cbbrowne at ca.afilias.info> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Depends on| |179 --- Comment #3 from Christopher Browne <cbbrowne at ca.afilias.info> 2010-12-16 08:54:45 PST --- Further discussion showing that it's problematic to consider the cases where this should cause the slon to terminate with fatal error. The trouble is that there is little certainty in the determination that things are well and truly broken. 1. There isn't a straightforward way to indicate that a node is being "shunned" due to failover. 2. It may be that one or the other of the disagreeing nodes is simply behind in processing events from other places, and the contradiction may shortly clear itself up. There's no straightforward way to determine either. Once more of the "automated WAIT FOR" logic is in place, we may have clearer answers; attaching dependency and deferring... -- 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.
- Previous message: [Slony1-bugs] [Bug 171] Health Check: Verify node's parentage
- Next message: [Slony1-bugs] [Bug 171] Health Check: Verify node's parentage
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list