Bug 1733377 - Document pacemaker's new fence-action cluster property
Summary: Document pacemaker's new fence-action cluster property
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-High_Availability_Add-On_Reference
Version: 7.8
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-25 21:00 UTC by Ken Gaillot
Modified: 2019-11-04 14:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-04 14:27:43 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ken Gaillot 2019-07-25 21:00:24 UTC
In RHEL 7.8 (and similarly for 8.2), "Chapter 12. Pacemaker Cluster Properties" will need a new entry:

Name: fence-reaction
Default: stop
Description: How a cluster node should react if notified of its own fencing. A cluster node may receive notification of its own fencing if fencing is misconfigured, or if fabric fencing is in use that doesn't cut cluster communication. Allowed values are "stop" to attempt to immediately stop pacemaker and stay stopped, or "panic" to attempt to immediately reboot the local node, falling back to stop on failure.


It might be helpful to elaborate on this in "Chapter 5. Fencing: Configuring Stonith". The default value is expected to change to "panic" in a future release of pacemaker (not expected in the lifetime of RHEL 7 and 8), because it is the safest choice. If anyone prefers the stop behavior, it is recommended to set it explicitly in the configuration. Preferring the stop behavior is most likely to happen in conjunction with fabric fencing, but I see we don't have anything specifically about fabric fencing currently.

Unrelated, but there is another property missing from the table:

Name: cluster-name
Default: (empty)
Description: An arbitrary name for the cluster. This optional value is mostly for users' convenience as desired in administration, but may also be used in Pacemaker configuration rules via the #cluster-name node attribute, and by higher-level tools and resource agents.

"pcs property set" will print an error and require --force for this property before RHEL 7.8/8.2, but that will be fixed as of those versions.


Note You need to log in before you can comment on or make changes to this bug.