Maintenance and updates for your Aiven for MySQL® service
Manage maintenance updates and set the maintenance window for your Aiven for MySQL® service.
Maintenance updates
Aiven applies some maintenance updates automatically. Aiven provides two types of updates:
- Mandatory updates: Security updates, quarterly patch releases, and platform updates that affect reliability or stability of the service nodes.
- Optional updates: All updates other than mandatory ones are initially optional. After six months, they become mandatory and are applied in the next week’s maintenance window at the earliest.
Advance notice is provided for all updates. You have at least seven days’ notice before an update is applied, except for critical security updates, which may be applied in the current week’s window.
During service upgrades, maintenance updates are applied automatically and do not require your action.
When a mandatory service update for Apache Kafka® is released, the Kafka upgrade procedure runs automatically.
You can check pending updates using:
- Aiven Console: Service settings > Service management
- Aiven CLI:
avn service getcommand - Aiven API:
serviceendpoint
Maintenance window
A maintenance window defines when Aiven can automatically apply maintenance updates to a service. Set the window by choosing a day of the week and a start time (UTC) for each service. Maintenance can begin any time after the configured start time.
Aiven uses maintenance windows to apply routine updates such as operating system patches, security fixes, and minor version upgrades. During maintenance, Aiven may restart or replace service nodes. This can cause brief connection interruptions, but services are designed to minimize downtime.
Aiven performs maintenance in a rolling-forward style, creating new nodes alongside existing ones and retiring the old nodes after the upgrade completes.
Major service upgrades are triggered manually. A manually triggered upgrade starts immediately, regardless of the maintenance window.
When an update becomes available, Aiven schedules it for the next available maintenance window for each service.
- Each service follows its own configured day and time.
- The update runs in the first window that occurs after it becomes available.
Example
| Service | Maintenance window |
|---|---|
| Non-production | Monday 12:00 UTC |
| Production | Wednesday 12:00 UTC |
If an update becomes available on Tuesday, production updates on Wednesday and non-production the following Monday.
You cannot control the order in which services are updated. Each service updates according to its own configured maintenance window, and there is no guaranteed way to control the update sequence. Manual updates and maintenance window adjustments only help for non-critical updates.
Set the maintenance window
To set the maintenance window for your service:
- Console
- Terraform
- In the Aiven Console, open your service.
- On the Overview page, scroll to the Maintenance section.
- Click Actions > Change maintenance window.
- Set the day and time, then click Save changes.
Use the maintenance_window_dow and maintenance_window_time attributes in
your Aiven service resource.
Periodic infrastructure updates
Maintenance updates are scheduled automatically for services with nodes active for 180 days and more.
Periodic infrastructure updates are mandatory for all the services except for those with maintenance disabled.
Related pages