Skip to main content

​
Overview

A maintenance window defines a recurring time slot during which RisingWave Cloud may perform automated operations on your cluster. Currently, the primary automated operation is version upgrades for clusters running deprecated RisingWave versions. When a version you are running reaches end-of-support (see release support policy), RisingWave Cloud will automatically schedule an upgrade to a supported version. The upgrade is executed only during your configured maintenance window.

​
Default maintenance window

All clusters are assigned a default maintenance window:

​
Configure your maintenance window

​
During cluster creation

The maintenance window is shown on the cluster confirmation screen before you create your cluster. Click the gear icon to open the Maintenance rules dialog and adjust the settings.
Maintenance window shown on the cluster creation confirmation screen

​
From an existing cluster

To update the maintenance window for an existing cluster:
  1. Go to the RisingWave Cloud dashboard, open your cluster, and select Maintenance in the cluster navigation.
  2. Click Modify rules to open the Maintenance rules dialog.
  3. Adjust the settings and click Confirm.
Maintenance tab showing current rules and maintenance log
Maintenance rules dialog for an existing cluster

​
Settings

​
How automated upgrades work

When your cluster is running a deprecated version, RisingWave Cloud schedules an upgrade as follows:
  1. Detection — The system identifies clusters running versions below the minimum supported threshold.
  2. Scheduling — An upgrade plan is created and scheduled for the start of your next maintenance window.
  3. Execution — During the maintenance window, the upgrade runs. If your cluster is stopped, it is temporarily started for the upgrade and then returned to the stopped state afterward.
  4. Retry — If an upgrade attempt fails, it is rescheduled for the next maintenance window. Up to 3 attempts are made before the plan is marked as failed and the team is alerted.
Additional behaviors:
  • A cluster will not have more than one automated upgrade attempt per calendar week.
  • A pre-upgrade backup is taken automatically before the upgrade runs.
  • Clusters running pre-release or tagged versions (e.g., release candidates) are not eligible for automated upgrades.

​
View upcoming and past maintenance

The Maintenance tab shows both the next scheduled upgrade and a log of past maintenance operations. When an upgrade has been scheduled, a banner at the top of the tab shows the upcoming maintenance time and the target version.
Maintenance tab showing an upcoming scheduled upgrade with details expanded
Click Show details to expand the banner and see the target version and scheduled time. The Maintenance Log section below shows the history of past automated upgrade attempts, including the target version, scheduled time, outcome, and duration.

​
Opting out or freezing upgrades

To freeze upgrades or switch to manual-only mode, reach out via Slack. When automated upgrades are disabled, you are responsible for upgrading your cluster before its version reaches end-of-support. See Update RisingWave version and the release support policy for details.