ApsaraMQ for RocketMQ provides a fully managed version management service. If a new broker version is available, the system automatically updates the version of your instance in the backend. The update does not impact message sending or receiving. You can change the execution time and maintenance window of an automatic version update task based on your business fluctuations.
Limits
The version management feature is available only for Enterprise Platinum Edition instances.
Impacts
In most cases, a version update requires less than 30 minutes to complete. During the update, brokers are restarted in batches. This may cause transient connections on clients, but messages can be sent and received as expected.
During a version update, you cannot perform operations such as unsubscribing from an instance, releasing an instance, or downgrading or upgrading instance configurations. However, you can renew an instance. For more information, see Unsubscription process, Overview, Procedure, and Manual renewal.
After an instance version is updated, you cannot roll back the instance to a previous version.
Scope of version updates
The full version number of an ApsaraMQ for RocketMQ instance is in the x.y-rmq-yyyymmdd format. The following items describe the detailed information about version numbers:
x.y: corresponds to the open source Apache RocketMQ version number x.y.z. z indicates the latest version. For example, 5.1 corresponds to the latest Apache RocketMQ version 5.1.z.
yyyymmdd: corresponds to the version number of the Commercial Edition of ApsaraMQ for RocketMQ. Example: 20230329. The Commercial Edition of ApsaraMQ for RocketMQ includes feature changes, feature optimizations, and bug fixes.
Examples:
Update a 5.0-rmq-20230329 instance to 5.1-rmq-20230329
Update a 5.0-rmq-20230329 instance to 5.0-rmq-20230411
For information about the updated content of each broker version, see Release notes for ApsaraMQ for RocketMQ 5.x.
Rules of version updates
Update method
Automatic update: By default, ApsaraMQ for RocketMQ automatically updates instance versions. After a new ApsaraMQ for RocketMQ broker version is released, the system creates a version update task and completes the task in the backend.
Version update tasks
Version update tasks are automatically created by ApsaraMQ for RocketMQ. You can view the details of a version update task, such as the status and execution time of the task, in the ApsaraMQ for RocketMQ console. For more information, see Change the execution time of a version update task.
Task Source | Scheduled Execution Time | Latest Execution Time | Cancelable or Not | Time Change Supported or Not | Task Generation Time |
Automatic update triggered by version iteration | The start time of the most recent maintenance window on the day when the new version is released. | Seven days after the scheduled execution time | No | Yes | The task is immediately generated after the update announcement is released. |
Maintenance window
Version updates are automatically performed during the default maintenance window that ranges from 02:00 to 06:00.
You can specify a custom maintenance window. For more information, see Change the maintenance window of a version update task.
The changed maintenance window takes effect only on version update tasks that are generated after the change.
If the start time and end time that you specify for the maintenance window are the same, the update task can be executed at any time on the day.
If the end time that you specify is earlier than the start time, the maintenance window ends at the specified time on the next day. For example, if you set the start time to 11:00 and the end time to 02:00, the update task can be executed between 11:00 of the current day and 02:00 of the next day.
Version validity period
The version validity period of an ApsaraMQ for RocketMQ instance is 6 months.
Destination versions
By default, an ApsaraMQ RocketMQ instance is updated to the latest version, regardless of whether multiple versions are available.
Change the execution time of a version update task
Log on to the ApsaraMQ for RocketMQ console. In the left-side navigation pane, click Instances.
In the top navigation bar, select a region, such as China (Hangzhou). On the Instances page, click the name of the instance that you want to manage.
On the Instance Details page, click the Version Management tab.
On the Version Management tab, click the Pending Tasks tab.
Find the task that you want to manage in the pending task list and click Change Time in the Actions column.
In the Modify Pending Task Update Time panel, configure the Newly Scheduled Update Time parameter and click OK.
Change the maintenance window of an update task
Log on to the ApsaraMQ for RocketMQ console. In the left-side navigation pane, click Instances.
In the top navigation bar, select a region, such as China (Hangzhou). On the Instances page, click the name of the instance that you want to manage.
On the Instance Details page, click the Version Management tab. In the upper-right corner, click Update Configuration.
In the Modify Version Update Configurations panel, change the maintenance window and click OK.
References
For information about the updated content of each ApsaraMQ for RocketMQ broker version, see Release notes for ApsaraMQ for RocketMQ 5.x.