ApsaraMQ for Kafka supports major versions 0.10.x, 2.2.0, and 2.6.2. Upgrade to a newer version to access performance improvements, bug fixes, and new features while maintaining compatibility with your existing SDKs and API operations.
How it works
ApsaraMQ for Kafka supports two types of version upgrades:
| Upgrade type | Description | Example |
|---|---|---|
| Major version upgrade | Upgrades the instance from one major version to another. | 0.10.x to 2.x |
| Minor version update | Applies bug fixes and performance optimizations within the same major version. | 2.2.0 to kernel-optimized 2.2.0 |
Major version 0.10.x includes minor versions 0.10 and 0.10.2.
Rolling upgrade process
During an upgrade, nodes are upgraded one at a time in a rolling fashion. Each node is verified before the next one begins. In normal cases, this approach keeps the instance available throughout the process.
The following sequence describes what happens during the upgrade:
A single node begins the upgrade process.
The node is upgraded and restarted.
The system verifies that the upgraded node is healthy before proceeding.
The next node is upgraded, and the process repeats until all nodes are complete.
Because nodes are upgraded sequentially, the cluster remains available. Producers and consumers may experience brief disconnections as individual nodes restart, but Kafka clients automatically reconnect and retrieve updated metadata.
Before you begin
Upgrades are free of charge and compatible with existing SDKs and API operations.
Make sure that:
The ApsaraMQ for Kafka instance is in the Running state
Your client supports automatic reconnection and can handle brief disconnections (Kafka clients support this by default)
Recommendations
Test the upgrade on a non-production instance before upgrading your production instance.
Schedule upgrades during off-peak hours to minimize the impact of brief reconnections.
After a major version upgrade, upgrade your client version to keep the client and broker versions consistent. After a minor version update, no client update is needed.
The message storage format of version 2.x differs from version 0.10.x. After upgrading from 0.10.x to 2.x, you cannot roll back to 0.10.x. Proceed with caution.
Newly deployed ApsaraMQ for Kafka instances run version 2.x. Existing 0.10.x instances continue to work as expected.
Estimated upgrade duration
The upgrade duration depends on the computing specification of the instance.
For instances using the alikafka.hr.30xlarge or alikafka.hw.30xlarge specification, or a lower specification:
| Upgrade type | Estimated duration |
|---|---|
| Major version upgrade | ~25 minutes |
| Minor version update | ~15 minutes |
Upgrade an instance
Log on to the ApsaraMQ for Kafka console. In the Resource Distribution section of the Overview page, select the region where the instance resides.
On the Instances page, click the name of the instance.
In the Basic Information section of the Instance Details page, start the upgrade:
To perform a major version upgrade, click Major Version Upgrade next to Major Version.
To perform a minor version update, click Minor Version Update next to Minor Version.
In the panel that appears, complete the following steps:
Read the content in the Read Before Upgrade section.
Enter your name in the Emergency Contact field.
Enter your emergency phone number in the Emergency Contact Number field.
Select the upgrade time in the Started At field.
Click Confirm.
After you click OK, the instance is upgraded immediately or at the scheduled time within seven days.
What to expect during the upgrade
During the upgrade, you may observe the following behavior. These effects are temporary and resolve as the upgrade completes.
| Behavior | Details |
|---|---|
| Client disconnection messages | Error messages indicating the client is disconnected from a node may appear in application logs. The client automatically reconnects and retrieves the latest metadata. No manual intervention is required. |