Operations such as configuration upgrades, downgrades, and scheduled elasticity policy runs trigger instance restarts on ApsaraMQ for Kafka. Track restart task progress, type, and outcome on the Task Execution Records tab in the ApsaraMQ for Kafka console.
Prerequisites
Before you begin, ensure that you have:
A serverless ApsaraMQ for Kafka instance in the Running state
View task execution records
Log on to the ApsaraMQ for Kafka console. In the Resource Distribution section of the Overview page, select the region where the ApsaraMQ for Kafka instance that you want to manage resides.
On the Instances page, click the name of the instance that you want to manage.
On the Instances page, click the name of your instance.
On the Instance Details page, click the Task Execution Records tab.
The tab displays the type, status, start time, and end time of each restart task.
Task types
| Value | Description |
|---|---|
| Instance Upgrade or Downgrade | The instance edition, network type, Internet traffic, reserved capacity for message publishing, or reserved capacity for message subscription was changed. For more information, see Upgrade and downgrade instance configurations. |
| Configuration Upgrade or Downgrade | A scheduled elasticity policy adjusted the reserved capacity for message production and consumption to handle traffic spikes. For more information, see Elasticity policies. |
Task statuses
| Value | Description |
|---|---|
| Not Executed | The task is scheduled but has not started. |
| Executing | The task is in progress. |
| Executed | The task completed successfully. |
| Canceled | The task was canceled before completion. |