All Products
Search
Document Center

PolarDB:Task center

Last Updated:Mar 28, 2026

Task Center gives you a single place to monitor the progress and history of long-running PolarDB cluster operations—backups, restores, failovers, node changes, and more. Instead of polling individual cluster pages, you can filter and track all tasks from a centralized view.

Supported editions

Task Center is available for PolarDB for MySQL Enterprise Edition and Standard Edition clusters only.

Limitations

  • Task history is only available for tasks that ran after Task Center was released (March 15).

  • Only tasks from the last 30 days are shown.

  • PolarProxy tasks are not tracked—this includes upgrading PolarProxy and changing cluster or custom endpoints.

  • Task Center is view-only. You cannot modify the switching time or retry a task.

Supported task types

Task Center displays running tasks and completed tasks from the last 30 days. Use the Task Type filter to narrow results.

The following task types are tracked for PolarDB for MySQL:

PolarDB for MySQL

Task typeTask nameEnterprise EditionStandard EditionNotes
create clusterCreate a clusterSupportedSupportedNew cluster creation only. Tasks for migrating data from ApsaraDB RDS are not tracked.
Data Recovery (Full)Method 1: Restore from a backup set (level-1 backup)SupportedSupportedEnterprise Edition: Cluster Edition and Multi-master Cluster (Database/Table) Edition only. Standard Edition: level-2 backup with PSL4 or PSL5 storage only.
Method 2: Restore to an earlier point in time (level-1 backup)SupportedSupported
Method 1: Restore from a backup set (level-2 backup)SupportedSupported
Method 2: Restore to an earlier point in time (level-2 backup)SupportedSupported
Library Table RecoveryRestoration of individual databases and tablesSupportedSupported
clone clusterClone a clusterSupportedNot supportedEnterprise Edition: Cluster Edition only.
specification change or migrationChange node specificationsSupportedSupported
kernel version upgradeMinor version updatesSupportedSupported
Add NodeAdd or remove read-only nodesSupportedSupported
Delete NodeAdd or remove read-only nodesSupportedSupported
cluster master backup switchAutomatic failover and manual failoverSupportedSupported
Cluster SwitchChange the primary zoneSupportedSupported
delete clusterRelease a clusterSupportedSupported
parameter adjustmentSpecify cluster and node parametersSupportedSupported
account changeCreate a privileged account / Modify / DeleteNot supportedSupported
Storage Online ExpansionStorage capacity scale-upNot supportedSupported
restart clusterManage nodesSupportedSupported
configuration changeChange ESSD storage typesNot supportedSupported
Configure TDE for a PolarDB for MySQL clusterSupportedSupported
Configure SSL encryptionSupportedSupported
Network ChangesCreate a primary endpointSupportedSupportedCluster endpoint and custom endpoint changes are not tracked.
Modify the primary endpointSupportedSupported
Delete the primary endpointSupportedSupported

View task progress

Task Center shows step-level progress for long-running operations such as data recovery and library table recovery.

Progress and status updates are displayed with a delay. Manually refresh the task list to see the latest status. On the Task Details page, progress can update automatically or manually. After a long-running task completes, its description is cleared from the Task Details page.
  1. Log on to the PolarDB console. In the left-side navigation pane, click Task Management > Task Center.

  2. Filter tasks by start time, keyword (task ID or resource ID), or task status.

    image

  3. Find the task and click Details in the Actions column.

The Task Details page shows step names and progress remarks for Library Table Recovery and Data Recovery tasks:

Task typeTask nameSteps (Enterprise Edition)Steps (Standard Edition)Example remark
Library Table RecoveryRestoration of individual databases and tablesRestore incremental data to temporary node (if needed)Restore incremental data to temporary node (if needed)Playing back the 16th Redo Log (ib_logfilexxx), a total of 50 Redo Logs need to be played back
Restore tables on primary node / Restore tables on secondary node (if needed)Restoration of individual databases and tablesRestoring the 16th table (database name/table name), a total of 50 tables need to be restored
Data restorationRestore to an earlier point in time (level-1 backup)Restore incremental dataRestore incremental dataPlaying back the 16th Redo Log (ib_logfilexxx), a total of 50 Redo Logs need to be played back
Restore from a backup set (level-2 backup)Restore full data on primary node / Restore full data on secondary node (if needed)Full restorationRecovery progress 32%
Restore to an earlier point in time (level-2 backup)Restore full data on primary node / Restore full data on secondary node (if needed)Full restorationRecovery progress 32%
Incremental data restoreRestore incremental dataRestore incremental dataPlaying back the 16th Redo Log (ib_logfilexxx), a total of 50 Redo Logs need to be played back
image

FAQ

Why is my task progress stuck?

Task progress is shown as a percentage and does not advance linearly. The rate depends on task type, data volume, workload, and host resources. If progress appears unchanged for an extended period, a time-consuming backend operation is likely in progress. For library table recovery and data recovery tasks, check the Description section on the Task Details page for step-level progress details.

Why doesn't my task appear in Task Center after I perform an operation?

Check whether the operation is listed in Supported task types. Operations not on that list are not tracked. Tasks that ran before Task Center was released also do not appear. For supported operations, there may be a short delay before the task appears—refresh the page to see the latest status.

Can I cancel a running task?

No. Running tasks cannot be cancelled because they are tied to backend operations such as data migration, refunds, and switchovers. Wait for the task to complete.

Why is the task still running after my cluster reaches the Running state?

A cluster in the Running state is ready for use. The cluster creation task may still be running because it performs post-processing steps such as resource recycling and secondary zone creation. These steps do not affect the cluster.

I did not enable Hot Standby Cluster, but the task shows steps for secondary zones.

The backend task covers all possible scenarios. Steps that do not apply to your configuration are automatically skipped. The task completes normally without those steps.