Four common Maintenance Mode Use Cases follow:
You want to perform hardware, firmware, or OS maintenance on a host.
You want to:
Prevent alerts generated by all components on this host.
Be able to stop, start, and restart each component on the host.
Prevent host-level or service-level bulk operations from starting, stopping, or restarting components on this host.
To achieve these goals, turn On Maintenance Mode explicitly for the host. Putting a host in Maintenance Mode implicitly puts all components on that host in Maintenance Mode.
You want to test a service configuration change. You will stop, start, and restart the service using a rolling restart to test whether restarting picks up the change.
You want:
No alerts generated by any components in this service.
To prevent host-level or service-level bulk operations from starting, stopping, or restarting components in this service.
To achieve these goals, turn on Maintenance Mode explicitly for the service. Putting a service in Maintenance Mode implicitly turns on Maintenance Mode for all components in the service.
You turn off a service completely.
You want:
The service to generate no warnings.
To ensure that no components start, stop, or restart due to host-level actions or bulk operations.
To achieve these goals, turn On Maintenance Mode explicitly for the service. Putting a service in Maintenance Mode implicitly turns on Maintenance Mode for all components in the service.
A host component is generating alerts.
You want to:
Check the component.
Assess warnings and alerts generated for the component.
Prevent alerts generated by the component while you check its condition.
To achieve these goals, turn on Maintenance Mode explicitly for the host component. Putting a host component in Maintenance Mode prevents host-level and service-level bulk operations from starting or restarting the component. You can restart the component explicitly while Maintenance Mode is on.
