Maintenance in Managed Service for OpenSearch

Maintenance includes:

• Automatic installation of OpenSearch updates and patches for host groups (including for stopped clusters).
• Scheduled automatic storage expansion.
• Other maintenance activities.

A major DBMS version update is not part of maintenance. For more information about upgrading between major versions, see OpenSearch version upgrade.

Maintenance windowMaintenance window

You can set the maintenance window when creating a cluster or updating its settings:

• The At any time option (default) allows performing maintenance at any time.
• The By schedule option allows you to select the day of the week and UTC time interval for the maintenance. For example, you can choose a time when the cluster is least loaded.

Both active and stopped clusters are subject to maintenance. Maintenance operations may include DBMS updates, applying patches, etc.

In the management console, you select the maintenance start time as an hour interval. In other interfaces, you specify this interval by its sequence number, from 1 to 24.

For example, to start maintenance in the interval from 00:00 to 01:00, put 1; from 04:00 to 05:00, 5.

Maintenance workflowMaintenance workflow

In Managed Service for OpenSearch single-host clusters, a single host undergoes maintenance. This means, if you restart such a cluster during maintenance, it will become unavailable.

In multi-host clusters, hosts undergo maintenance one by one. Such hosts are queued randomly. Any host that requires a restart during maintenance will be unavailable until maintenance is complete. If you access a cluster using the FQDN of the OpenSearch host, the cluster may become unavailable. To make your application continuously available, access the cluster using a special FQDN always pointing to the available host.