In a fully-managed serverless architecture, planned maintenance on the underlying infrastructure—such as system upgrades, node rotation, and hot migration—can cause brief failovers for running jobs. Maintenance windows let you restrict these planned changes to specific time frames, keeping disruptions out of peak business hours.
The Control Center provides two complementary features:
-
Maintenance window: A time frame you define for the platform to perform changes on underlying resources. During a maintenance window, the platform can perform operations such as seamless migration and node rotation. Outside this window, all planned changes are automatically postponed until the next window.
-
Maintenance events: A centralized log of planned maintenance operations initiated by the platform, including Elastic Compute Service (ECS) instance maintenance, node rotation, and host machine hot migration. Each event provides a full lifecycle view, enabling post-event auditing and review.
Maintenance windows apply at the project space level, affecting all resources within that space.
If no maintenance windows are configured, the platform uses a default policy: changes can occur daily from 02:00 to 06:00 (UTC+8).
Prerequisites
Before you begin, ensure that you have:
-
Activated Realtime Compute for Apache Flink. For more information, see Activate Realtime Compute for Apache Flink.
-
Owner or Admin permissions for the target project space.
Create a maintenance window
-
In the navigation pane on the left, click Maintenance.
-
On the Maintenance Window tab, click Create Window.
-
Configure the following parameters.
Parameter Description Window name The name of the maintenance window. The name must be 2 to 200 characters long and can contain Chinese characters, letters, digits, and the following special characters: -._.Resource scope The scope affected by the maintenance window. Currently, only All (project space-level) is supported, which means the window applies to all resources in the current project space. Recurrence The frequency of the maintenance window. Select Daily, Weekly, or Monthly. For Weekly, specify the days of the week. For Monthly, specify the dates of the month. If a selected date does not exist in a given month (for example, the 31st), the window is inactive for that month. Time range (UTC) The start and end time for each maintenance window, specified in UTC. The console also displays the corresponding local time (UTC+08:00) for reference. NoteEach window must be at least one hour long. Cross-day windows (for example, 23:00 to 01:00) are supported. For monthly recurrence, select at least five maintenance days per month, and keep the interval between any two consecutive maintenance days within seven days, including across months.
Enable Specifies whether to activate the maintenance window immediately. If enabled, the window takes effect as soon as you save the configuration. If disabled, the configuration is saved but remains inactive until you enable it. -
Click OK.
Manage maintenance windows
The maintenance window list shows the name, resource scope, time range, and status of each window. From this list, you can:
-
Details: View the complete configuration of a window and its associated maintenance event history.
-
Edit: Modify the name, time range, or enabled status.
-
Delete: Remove the window. If all custom windows are deleted, the platform reverts to the default policy (02:00 to 06:00 daily, UTC+8).
If the current time falls outside all active maintenance windows, a notification appears at the top of the page indicating that all planned changes have been postponed until the next window.
View maintenance events
Switch to the Maintenance Events tab to view planned maintenance events that have occurred or are scheduled within the last 30 days.
Event list
| Field | Description |
|---|---|
| Event name | The name of the underlying engine maintenance event. |
| Event type | The source of the event, such as Flink maintenance, planned ECS maintenance, or unexpected ECS instance downtime. |
| Trigger time | The time the event is scheduled to occur or has already occurred. |
| Event status | The current status of the event: Completed (maintenance succeeded and the job has recovered), Scheduled (pending execution), Postponed (event fell outside a maintenance window and has been delayed to the next one), or Manual Intervention Required (maintenance failed or timed out—restart the job manually). |
| Affected jobs | The number of jobs affected. Click the number to view specific jobs and their recovery status. |
Event details
Click View Details for an event to see:
-
Basic information: Event source, scheduled execution period, and trigger time.
-
Window matching status: Whether the event occurred within a configured maintenance window.
-
Affected job analysis: A list of affected jobs and their current status.
-
Event history: The complete lifecycle log of the event.
Configure maintenance event notifications
Configure alert notifications to stay informed about important maintenance events.
-
Standard notifications: Sent when a maintenance event changes status—for example, when it is about to start, has completed, or has been postponed.
-
Forced change notifications: When a maintenance event falls outside all maintenance windows and fewer than 24 hours remain before its final execution deadline, the platform forces the change and notifies you through a console pop-up and a top banner.
FAQ
What happens if multiple maintenance windows overlap?
Overlapping windows are merged into a single continuous period. The platform can perform maintenance during the entire combined time range.
Why was a change postponed?
When a planned maintenance event is scheduled outside all configured maintenance windows, it is automatically deferred to the next available window. Check the Maintenance Events tab—postponed events show a status of Postponed.
Do maintenance windows support job-level control?
Not yet. Maintenance windows are currently set at the project space level only. Job-level control is planned for a future release.
How do cross-day maintenance windows work?
A cross-day window (for example, 23:00 to 01:00) is treated as a continuous period from 23:00 on the specified day to 01:00 on the following day.