File jsc#ECO-1611-0001-Feature-scheduler-add-priorit... of Package pacemaker.27560

Overview Repositories Revisions Requests Users Attributes Meta

File jsc#ECO-1611-0001-Feature-scheduler-add-priority-fencing-delay-cluster-1.1.patch of Package pacemaker.27560

From fb48eaa53e8a4b1dd116394e40bae1671a182b5a Mon Sep 17 00:00:00 2001
From: "Gao,Yan" <ygao@suse.com>
Date: Tue, 17 Mar 2020 12:13:52 +0100
Subject: [PATCH 01/15] Feature: scheduler: add priority-fencing-delay cluster
 option

This feature addresses the relevant topics and implements the ideas
brought up from:

https://github.com/ClusterLabs/fence-agents/pull/308

This commit adds priority-fencing-delay option (just the option, not the
feature itself).

Enforce specified delay for the fencings that are targeting the lost
nodes with the highest total resource priority in case we don't
have the majority of the nodes in our cluster partition, so that
the more significant nodes potentially win any fencing match,
which is especially meaningful under split-brain of 2-node
cluster. A promoted resource instance takes the base priority + 1
on calculation if the base priority is not 0. If all the nodes
have equal priority, then any pcmk_delay_base/max configured for
the corresponding fencing resources will be applied. Otherwise as
long as it's set, even if to 0, it takes precedence over any
configured pcmk_delay_base/max. By default, priority fencing
delay is disabled.
---
 include/crm/msg_xml.h |  1 +
 lib/pengine/common.c  | 17 +++++++++++++++++
 2 files changed, 18 insertions(+)

Index: pacemaker-1.1.19+20181105.ccd6b5b10/include/crm/msg_xml.h
===================================================================
--- pacemaker-1.1.19+20181105.ccd6b5b10.orig/include/crm/msg_xml.h
+++ pacemaker-1.1.19+20181105.ccd6b5b10/include/crm/msg_xml.h
@@ -377,6 +377,7 @@
 #  define XML_CONFIG_ATTR_ELECTION_FAIL	"election-timeout"
 #  define XML_CONFIG_ATTR_FORCE_QUIT	"shutdown-escalation"
 #  define XML_CONFIG_ATTR_RECHECK	"cluster-recheck-interval"
+#  define XML_CONFIG_ATTR_PRIORITY_FENCING_DELAY "priority-fencing-delay"
 
 #  define XML_ALERT_ATTR_PATH		"path"
 #  define XML_ALERT_ATTR_TIMEOUT	"timeout"
Index: pacemaker-1.1.19+20181105.ccd6b5b10/lib/pengine/common.c
===================================================================
--- pacemaker-1.1.19+20181105.ccd6b5b10.orig/lib/pengine/common.c
+++ pacemaker-1.1.19+20181105.ccd6b5b10/lib/pengine/common.c
@@ -115,6 +115,23 @@ pe_cluster_option pe_opts[] = {
 	  "Allow performing fencing operations in parallel", NULL },
 	{ "startup-fencing", "startup_fencing", "boolean", NULL, "true", &check_boolean,
 	  "STONITH unseen nodes", "Advanced Use Only!  Not using the default is very unsafe!" },
+    {
+        XML_CONFIG_ATTR_PRIORITY_FENCING_DELAY, NULL, "time", NULL,
+        NULL, &check_timer,
+        "Enforced fencing delay targeting the lost nodes with the highest total resource priority",
+        "Enforce specified delay for the fencings that are targeting the lost "
+            "nodes with the highest total resource priority in case we don't "
+            "have the majority of the nodes in our cluster partition, so that "
+            "the more significant nodes potentially win any fencing match, "
+            "which is especially meaningful under split-brain of 2-node "
+            "cluster. A promoted resource instance takes the base priority + 1 "
+            "on calculation if the base priority is not 0. If all the nodes "
+            "have equal priority, then any pcmk_delay_base/max configured for "
+            "the corresponding fencing resources will be applied. Otherwise as "
+            "long as it's set, even if to 0, it takes precedence over any "
+            "configured pcmk_delay_base/max. By default, priority fencing "
+            "delay is disabled."
+    },
 
 	/* Timeouts etc */
 	{ "cluster-delay", "transition_idle_timeout", "time", NULL, "60s", &check_time,

Places

File jsc#ECO-1611-0001-Feature-scheduler-add-priority-fencing-delay-cluster-1.1.patch of Package pacemaker.27560

Places