This article introduces the PolarDB Task Center.
Overview
To help you manage tasks for your PolarDB clusters, track the progress of long-running tasks such as cluster backups and recoveries, and improve cluster O&M efficiency, PolarDB allows you to view the progress of current tasks and the details of historical tasks in .
Version requirements
The Task Center is available for PolarDB for MySQL Enterprise Edition and Standard Edition clusters.
Limitations
-
You can only view tasks that were created after the Task Center was launched on March 15, 2024.
-
You can only view task history from the last 30 days.
-
Tasks related to PolarProxy, such as version upgrades or changes to cluster endpoints and custom endpoints, are not tracked.
-
The Task Center is primarily a monitoring tool. Operations such as modifying the switchover time or retrying are available only for certain tasks.
Supported task types
In the PolarDB Task Center, you can view currently running tasks and completed tasks from the last 30 days.
PolarDB for MySQL
|
Task type |
Task name |
Enterprise edition |
Standard edition |
Notes |
|
Create cluster |
Supported |
Supported |
The Task Center tracks the creation of new clusters but does not track migrations from ApsaraDB RDS. |
|
|
Data recovery (full) |
Supported |
Supported |
|
|
|
Supported |
Supported |
|||
|
Supported |
Supported |
|||
|
Supported |
Supported |
|||
|
Library Table Recovery |
Supported |
Supported |
||
|
Clone cluster |
Supported |
Not available |
|
|
|
Specification change or migration |
Supported |
Supported |
||
|
Kernel version upgrade |
Supported |
Supported |
||
|
Add node |
Supported |
Supported |
||
|
Delete node |
Supported |
Supported |
||
|
Failover |
Supported |
Supported |
||
|
Cluster switchover |
Supported |
Supported |
||
|
Delete cluster |
Supported |
Supported |
||
|
Parameter adjustment |
Supported |
Supported |
||
|
Account change |
Not supported |
Supported |
||
|
Not supported |
Supported |
|||
|
Not supported |
Supported |
|||
|
Online storage expansion |
Not supported |
Supported |
||
|
Restart cluster |
Supported |
Supported |
||
|
Configuration change |
Not available |
Supported |
||
|
Supported |
Supported |
|||
|
Supported |
Supported |
|||
|
Network change |
Supported |
Supported |
Tasks for changing cluster endpoints or custom endpoints are not tracked. |
|
|
Supported |
Supported |
|||
|
Supported |
Supported |
You can use the Task type filter in the Task Center to find specific tasks.
View detailed task progress
-
Currently, only clusters of PolarDB for MySQL Standard Edition and Enterprise Edition support displaying the detailed progress of long-running tasks. When a long-running task is complete, its remarks are cleared.
-
In the Task Center list, you must manually refresh the page to see the latest task status and progress. In the Task Details view, progress information updates automatically, but you can also refresh it manually.
-
The display and update of progress for long-running tasks may be delayed.
-
Log on to the PolarDB console. In the left-side navigation pane, click .
-
You can filter tasks by criteria like start time, keywords (Task ID, Resource ID), and time range (1 hour, 1 day, 7 days, or 30 days). The page also shows task counts by status, such as Succeeded, Failed, Pending Intervention, and Running.
-
In the Actions column of the target task, click Details to view the Task Details page.
You can currently view detailed progress for tasks such as Library Table Recovery and data recovery. The following table describes these details.
Task type
Task name
Step name
Example
Enterprise edition
Standard edition
Library Table Recovery
Library Table Recovery
Incremental recovery on temporary node (on-demand)
Incremental recovery on temporary node (on-demand)
Replaying Redo Log 16 of 50 ( ib_logfilexxx ).
Library/Table recovery on primary node
Library/Table recovery on secondary node (on-demand)
Library Table Recovery
Restoring table 16 of 50 ( database_name.table_name ).
Data recovery
Point-in-time recovery (from a level-1 backup)
Incremental recovery
Incremental recovery
Replaying Redo Log 16 of 50 ( ib_logfilexxx ).
Restore from a level-2 backup set
Full recovery on primary node
Full recovery on secondary node (on-demand)
Full recovery
Recovery progress: 32%
Point-in-time recovery (from a level-2 backup)
Full recovery on primary node
Full recovery on secondary node (on-demand)
Full recovery
Recovery progress: 32%
Incremental recovery
Incremental recovery
Replaying Redo Log 16 of 50 ( ib_logfilexxx ).