maintenance_mode
during a scheduled maintenance window. This will keep the cluster running but not monitor, start, or stop resources during this time.
Example 8.20. Schedule a maintenance window for 9 to 11 p.m. CDT Sept. 20, 2019
<crm_config> <cluster_property_set id="cib-bootstrap-options"> <nvpair id="bootstrap-stonith-enabled" name="stonith-enabled" value="1"/> </cluster_property_set> <cluster_property_set id="normal-set" score="10"> <nvpair id="normal-maintenance-mode" name="maintenance-mode" value="false"/> </cluster_property_set> <cluster_property_set id="maintenance-window-set" score="1000"> <nvpair id="maintenance-nvpair1" name="maintenance-mode" value="true"/> <rule id="maintenance-rule1" score="INFINITY"> <date_expression id="maintenance-date1" operation="in_range" start="2019-09-20 21:00:00 -05:00" end="2019-09-20 23:00:00 -05:00"/> </rule> </cluster_property_set> </crm_config>
Important
cluster_property_set
with an id
set to "cib-bootstrap-options" will always have the highest priority, regardless of any scores. Therefore, rules in another cluster_property_set
can never take effect for any properties listed in the bootstrap set.