This topic describes the features of the Tasks page in the PolarDB console.
Overview
On the Tasks page in the PolarDB console, you can view the task progress and historical task details. You can view the progress of long-running tasks such as cluster backup and restore. This helps you manage PolarDB cluster tasks, and improve cluster O&M efficiency.
Supported versions
Only the tasks of a cluster of PolarDB for MySQL Enterprise Edition can be managed on the Tasks page.
Limitations
You can view only the task status after the release date of the Tasks page, which is March 15.
You can view only the historical tasks within the last 30 days.
You cannot view the status of PolarProxy tasks, such as upgrading PolarProxy, and changing a cluster endpoint or a custom endpoint.
You can only view the task progress. You cannot perform O&M operations such as modifying the switching time or performing retries.
Supported task types
The PolarDB Tasks page allows you to view the tasks that are running and historical tasks completed within the last 30 days.
The following task types are supported:
PolarDB MySQL
Task type | Task name | Enterprise Edition | Description |
create cluster | Supported | Only the tasks for creating new clusters are supported. The cluster creation tasks for data migration from ApsaraDB RDS are not supported. | |
Data Recovery (Full) | Method 1 for full restoration: Restore data from a backup set (based on level-1 backup) | Supported |
|
Method 2 for full restoration: Restore data to an earlier point in time (based on level-1 backup) | Supported | ||
Method 1 for full restoration: Restore data from a backup set (based on level-2 backup) | Supported | ||
Method 2 for full restoration: Restore data to an earlier point in time (based on level-2 backup) | Supported | ||
Library Table Recovery | Supported | ||
clone cluster | Supported |
| |
specification change or migration | Supported | ||
kernel version upgrade | Supported | ||
Add Node | Supported | ||
Delete Node | Supported | ||
cluster master backup switch | Supported | ||
Cluster Switch | Supported | ||
delete cluster | Supported | ||
parameter adjustment | Supported | ||
account change | Not supported | ||
Not supported | |||
Not supported | |||
Storage Online Expansion | Not supported | ||
restart cluster | Supported | ||
configuration change | Supported | ||
Supported | |||
Network Changes | Supported | The tasks for changing cluster endpoints or custom endpoints are not supported. | |
Supported | |||
Supported |
On the Tasks page, you can filter tasks by Task Type.
View the progress details of long-running tasks such as cluster backup and restore
Only the clusters of PolarDB for MySQL Enterprise Edition allows you to view the progress of long-term tasks. After a long-running task is complete, its description is cleared.
You need to manually refresh the task status and task progress on the Tasks page. The progress information on the Task Details page can be automatically or manually refreshed.
The progress and status update of a long-running task is displayed with a delay.
Log on to the PolarDB console. In the left-side navigation pane, click Tasks.
You can filter the tasks by start time, keyword (task ID, resource ID), and tasks status.
Find the task that you want to view and click Details in the Actions column.
You can view the details of tasks of the Library Table Recovery and Data Recovery types. See the following table for details:
Task type | Task name | Step name and description displayed on the Task Details page | |
Step name | Example remark | ||
Library Table Recovery | Restoration of individual databases and tables | 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) | Restoring the 16th table (database name/table name), a total of 50 tables need to be restored | ||
Data restoration | Restore data to an earlier point in time (based on level-1 backup) | Restore incremental data | Playing back the 16th Redo Log (ib_logfilexxx), a total of 50 Redo Logs need to be played back |
Restore data from a backup set (based on level-2 backup) | Restore full data on primary node Restore full data on secondary node (if needed) | Recovery progress 32% | |
Restore data to an earlier point in time (based on level-2 backup) | Restore full data on primary node Restore full data on secondary node (if needed) | Recovery progress 32% | |
Incremental restoration | Playing back the 16th Redo Log (ib_logfilexxx), a total of 50 Redo Logs need to be played back |
FAQ
Why is the progress of my task suspended?
The progress of your task is displayed in percentage and is not linearly changed. The progress varies based on different factors, such as the task type, data volumes, workloads, and resources of the hosts on which your cluster resides. In most cases, if the progress remains unchanged for a long period of time, time-consuming operations are being performed at the backend.
For long-running tasks such as individual database and table restoration and regular data restoration, the detailed progress of the step is displayed in the Description section of the step.
NoteOnly a cluster of PolarDB for MySQL Enterprise Edition allows you to view the progress of long-running tasks.
Why is my task not displayed on the Task Center page after I perform an operation on my cluster in the console?
You can check whether the operation that you performed on your cluster is supported by the Tasks page. If the operation is not supported, the task for the operation is not displayed on the Tasks page. For a supported task, the Tasks page may not display the task status right after you start the task. You need to wait for a while and refresh the page to see the task status.
Can I cancel an ongoing task on the Task Center page?
No, you cannot cancel an ongoing task on the Tasks page because ongoing tasks may be related to operations, such as refund, data migration at the backend, and switchover.
Why is the task still in progress when the cluster is in the Running state?
A cluster in the Running state is ready for normal use. The cluster creation task may be still in progress because it is performing post-processing operations such as resource recycling and secondary zone creation. These operations do not affect the use of the cluster.
I did not select Enable Hot Standby Cluster, but the task still contains the steps for secondary zones.
The background task is used in various scenarios. If a step is not required in the actual scenario, the background task automatically skips the step. The tasks is not affected.