Bug 173

Summary: Slonik ABORT command
Product: Slony-I Reporter: Christopher Browne <cbbrowne>
Component: slonikAssignee: Christopher Browne <cbbrowne>
Status: ASSIGNED ---    
Severity: enhancement CC: slony1-bugs
Priority: low    
Version: devel   
Hardware: All   
OS: All   

Description Christopher Browne 2010-12-03 13:33:17 UTC

Initially mentioned by Vivek Khera

General point: Fail if replication is behind

Reasonable criteria:
 - event count - "within 3 events is OK"
 - time interval "behind by no more than 15 seconds is OK"

Other Health Criteria
- Is node there?
- Is replication set there?
- Is subscription active?
- Run SQL, fail if ERROR
Comment 2 Christopher Browne 2011-01-27 09:21:03 UTC
Additional suggestion:

Are there any non-SYNC events outstanding?

Scripts that modify the cluster configuration may not care about how
far a node is behind in data, but definitely need to assume that the
current configuration is stable and not altered underneath by older
events, that haven't propagated through the cluster.  - Jan
Comment 3 Christopher Browne 2011-08-03 12:07:43 UTC
Perhaps this should be extended to a fuller "conditional" to mostly replace the present TRY block concept.  Have to think about that some more...
Comment 4 Christopher Browne 2011-08-08 12:40:40 UTC
As observed in bug #228, there would be some use in having conditionals used to pick between blocks of Slonik code.  We're not necessarily going to want to abort.