* Did some brief testing with Slony 1.2, 2.0 and 2.1 and appears to all work as expected.

[slony-i/slony_failover] / slony_failover.conf

diff --git a/slony_failover.conf b/slony_failover.conf
index f1be52a144a4dd25261d2a98705b8cd289810498..194c20b2a494aed644f9218abfe4e4abb26bc56d 100644 (file)
--- a/slony_failover.conf
+++ b/slony_failover.conf
@@ -87,3 +87,20 @@ autofailover_config_any_node = true         # After reading the initial cluster
 autofailover_poll_interval = 50             # Cluster state poll interval (milliseconds)
 autofailover_node_retry = 2                 # Retries before initiating failover
 autofailover_sleep_time = 5000              # Interval between retries (milliseconds)
+autofailover_perspective_sleep_time = 20000 # Interval between lag reads for failed nodes
+                                            # from surviving nodes. If greater than zero
+                                            # any observation that nodes have failed is
+                                            # checked from surviving nodes perspective by
+                                            # checking if lag times are extending.
+                                            # This does not guarantee 100% the nodes are down
+                                            # but if set to a large enough interval can back
+                                            # up our observation.
+autofailover_majority_only = true           # Only fail over if the quantity of surviving nodes
+                                            # is greater than the quantity of failed nodes.
+                                            # Intended to be used to prevent a split-brain scenario
+                                            # in conjunction with some other logic to monitor and 
+                                            # fence off the old origin if it is in the minority.
+autofailover_is_quorum = true               # If this script is running on a separate host set to 
+                                            # true to treat it as a quorum server. Effectively 
+                                            # increments sum of surviving nodes when calculating
+                                            # the majority above.