From 043aa641ad4373e96fd748deb1e7fab3cb579a07 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 17 Apr 2024 09:46:09 +0200 Subject: Merging upstream version 2.1.7. Signed-off-by: Daniel Baumann --- cts/cli/regression.daemons.exp | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'cts/cli/regression.daemons.exp') diff --git a/cts/cli/regression.daemons.exp b/cts/cli/regression.daemons.exp index 66bd7b3..b34fba8 100644 --- a/cts/cli/regression.daemons.exp +++ b/cts/cli/regression.daemons.exp @@ -122,6 +122,11 @@ Do not lock resources to a cleanly shut down node longer than this + + Fence nodes that do not join the controller process group within this much time after joining the cluster, to allow the cluster to continue managing resources. A value of 0 means never fence pending nodes. Setting the value to 2h means fence nodes after 2 hours. + How long to wait for a node that has joined the cluster to join the controller process group + + =#=#=#= End test: Get controller metadata - OK (0) =#=#=#= @@ -349,6 +354,11 @@ Apply fencing delay targeting the lost nodes with the highest total resource priority + + Fence nodes that do not join the controller process group within this much time after joining the cluster, to allow the cluster to continue managing resources. A value of 0 means never fence pending nodes. Setting the value to 2h means fence nodes after 2 hours. + How long to wait for a node that has joined the cluster to join the controller process group + + The node elected Designated Controller (DC) will consider an action failed if it does not get a response from the node executing the action within this time (after considering the action's own timeout). The "correct" value will depend on the speed and load of your network and cluster nodes. Maximum time for node-to-node communication -- cgit v1.2.3