Maintenance window is a time window during which we'll switch to new upgraded virtual machines and point the connection URI's DNS name at the new server.

Aiven service upgrades are performed in rolling forward style, which means that new service nodes are first created alongside with the older nodes one at a time, after which the old nodes are retired.

In case of MySQL, PostgreSQL and Redis the maintenance window usually lasts around 5-10 seconds. The downtime comes from old master stopping itself in a controlled manner and new master executing promotion sequence after this. Once the promotion is complete the old master node starts forwarding requests to the new master node so the service is accessible before DNS updates are propagated, though clients that end up reconnecting to the old master node will see additional disconnection once the old master is permanently retired.

In case of Kafka and Elasticsearch the service DNS address resolves to all the available service nodes. During an upgrade the DNS address changes to reflect the added and removed nodes. For example, a three node plan will have a minimum of three nodes available at all times during the whole upgrade operation.

Note: while the DNS name remains the same, the IP address it points to, will change during a maintenance break.

Did this answer your question?