Skip to content

Stopping the cluster services while in maintenance mode #465

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tahliar wants to merge 2 commits into
base: main
Choose a base branch
from
+19 −17
Open

Stopping the cluster services while in maintenance mode #465

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c7adb2b
Improved procedure for stopping cluster while in maintenance
tahliar Apr 23, 2026
3645e0a
Update revhist date
tahliar Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion xml/book_administration.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@
<info xmlns:d="http://docbook.org/ns/docbook">
<revhistory xml:id="rh-admin-part-maintenance">
<revision>
<date>2025-06-17</date>
<date>2026-04-23</date>
<revdescription>
<para/>
</revdescription>
Expand Down
34 changes: 18 additions & 16 deletions xml/ha_maintenance.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@
</dm:docmanager>
<revhistory xml:id="rh-cha-ha-maintenance">
<revision>
<date>2025-04-25</date>
<date>2026-04-23</date>
<revdescription>
<para/>
</revdescription>
Expand Down Expand Up @@ -630,7 +630,7 @@ Node <replaceable>&node2;</replaceable>: standby
</sect1>

<sect1 xml:id="sec-ha-maint-shutdown-node-maint-mode">
<title>Rebooting a cluster node while in maintenance mode</title>
<title>Stopping the cluster services while in maintenance mode</title>
<note>
<title>Implications</title>
<para>
Expand All @@ -654,36 +654,38 @@ Node <replaceable>&node2;</replaceable>: standby
</note>

<procedure xml:id="pro-ha-maint-reboot-node">
<title>Rebooting a cluster node while the cluster or node is in maintenance mode</title>
<title>Stopping the cluster services while the cluster or node is in maintenance mode</title>
<step>
<para>
On the node you want to reboot or shut down, log in as &rootuser; or
equivalent.
Log in as the &rootuser; user or as a user with <command>sudo</command> privileges.
</para>
</step>
<step>
<para>
If you have a DLM resource (or other resources depending on DLM), make
sure to explicitly stop those resources before stopping the cluster services:
sure to explicitly stop those resources before putting the cluster or the
node into maintenance mode. Stopping &pace; also stops the &corosync; service,
which DLM depends on. If &corosync; stops, the DLM resource assumes a split-brain
scenario and triggers a fencing operation.
</para>
<screen>&prompt.crm.res;<command>stop <replaceable>RESOURCE_ID</replaceable></command></screen>
<screen>&prompt.root;<command>crm --wait resource stop <replaceable>RESOURCE_ID</replaceable></command></screen>
<para>
The reason is that stopping &pace; also stops the &corosync; service on
whose membership and messaging services DLM depends. If &corosync; stops,
the DLM resource assumes a split-brain scenario and triggers a fencing
operation.
The <option>--wait</option> option makes sure the resource has really stopped
before the command returns.
</para>
</step>
<step>
<para>
Stop the cluster services on that node:
</para>
<screen>&prompt.root;<command>crm cluster stop</command></screen>
<para>
Put the cluster or the node into maintenance mode with one of the following commands:
</para>
<screen>&prompt.root;<command>crm maintenance on</command></screen>
<screen>&prompt.root;<command>crm node maintenance <replaceable>NODENAME</replaceable></command></screen>
</step>
<step>
<para>
Shut down or reboot the node.
Stop the cluster services on that node:
</para>
<screen>&prompt.root;<command>crm cluster stop</command></screen>
</step>
</procedure>
</sect1>
Expand Down