DM WebUI is a web-based GUI platform for managing TiDB Data Migration (DM) tasks. This platform provides a simple and intuitive way to manage a large number of migration tasks, which frees you from using the dmctl command-line tool.
This document introduces how to access DM WebUI, the prerequisites, the use cases of each page on the interface, and the attention points.
DM WebUI has the following pages:
- Task: Provides an entry to task creation, and displays the detailed information of each migration task. This page helps you monitor, create, delete, and configure migration tasks.
- Source: Configures the information of upstream data source for a migration task. On this page, you can manage the upstream configuration in a data migration environment, including creating and deleting upstream configuration, monitoring the task status corresponding to the upstream configuration, and modifying upstream configuration.
- Replication Detail: Displays the detailed status information of migration tasks. On this page, you can view the detailed configuration and status information based on a specified filter, including the configuration information and database names of the upstream and downstream, the relation of source tables and target tables.
- Members: Displays the list of all master and worker nodes in the DM cluster, and the binding relationship between worker nodes and the source. On this page, you can view the configuration information of the current DM cluster and the status information of each worker. In addition, basic management is also provided on this page.
The interface is as follows:
When OpenAPI is enabled, you can access the DM WebUI from any master node of the DM cluster. The access port is
8261 by default and is the same as that of DM OpenAPI. Here is an example of an access address:
Migration includes Source, Task, and Replication Detail pages.
Before creating a migration task, you need to create the data source information of the upstream for the replication task. You can create the upstream configuration in the Source page. When creating sources, pay attention to the following items:
- If there is a auto failover between primary and secondary instance, enable GTID in the upstream MySQL and set GTID to
Truewhen creating the upstream configuration; otherwise, the migration task will be interrupted during the failover (except for AWS Aurora).
- If a MySQL instance needs to be temporarily offline, you can disable the instance. However, when the MySQL instance is being disabled, other MySQL instances running migration tasks should not execute DDL operations; otherwise, the disabled instance cannot properly migrate data after it is enabled.
- When multiple migration tasks use the same upstream, it might cause additional stress. Enabling relay log can reduce the impact on the upstream, so it is recommended to enable relay log.
You can view the migration task details on the Task page, and create migration tasks.
In the task list, click the task name to view the Details page from the right. The Details page displays more detailed task status information. On this page, you can view the status of each sub-task and the current configuration information of the migration task.
In DM, each sub-task of a migration task might be at different stages, namely full dump -> full import (load) -> incremental replication (sync). Therefore, the current stage of a task is displayed with the statistics of the sub-task statuses, which can help you better understand the running status of the task.
To create a migration task on this page, click the Add button on the top right corner. You can use one of the following methods to create a migration task:
- By following the WebUI instruction. Fill in the required information step by step on the WebUI. This method is suitable for beginners and for daily use.
- By using a configuration file. Paste or write a JSON-formatted configuration file to create a migration task. This method supports adjusting more parameters and is suitable for advanced users.
You can view the status of the migration rules configured for a migration task on the Replication Detail page. This page supports querying by task, source, and database name.
The query result contains the corresponding information of the upstream table and the downstream table, so be careful using
.* in case that too many query results slow down the page response.
The Members page displays all the master and worker nodes in the DM cluster, and the binding relationship between worker nodes and the source.