Use DM in Kubernetes

    Note

    Make sure that the TiDB Operator version >= 1.2.0.

    Enable DM data migration tasks

    You can access the DM-master service using dmctl in the following two methods:

    Method #1: Attach to the DM-master or DM-worker Pod to use the built-in in the image.

    Method #2: Expose the DM-master service by accessing the DM cluster in Kubernetes and use dmctl outside the pods to access the exposed DM-master service.

    The differences between Method #1 and Method #2 are that the file locations of source.yaml and task.yaml are different, and that in Method #2 you need to configure the exposed DM-master service address in the master-addr configuration item of dmctl.

    Attach to the DM-master Pod by executing the following command:

    1. Write MySQL-1 related information to source1.yaml file, which can refer to .

    2. Configure the from.host in the source1.yaml file as the MySQL host address that the Kubernetes cluster can access internally.

    3. Configure the in the source1.yaml file as a subdirectory of the persistent volume in the Pod mount /var/lib/dm-worker directory. For example, /var/lib/dm-worker/relay.

      1. /dmctl --master-addr ${dm_cluster_name}-dm-master:8261 operate-source create source1.yaml

    1. Edit task configuration file task.yaml, which can refer to Configure the data migration task.

    2. Configure the target-database.host in as the TiDB host address that the Kubernetes cluster can access internally. If the cluster is deployed by TiDB Operator, configure the host as ${tidb_cluster_name}-tidb.${namespace}.

    3. In the task.yaml file, take the following steps:

      • Add the loaders.${customized_name}.dir field as the import and export directory for the full volume data, where ${customized_name} is a name that you can customize.
      • Configure the loaders.${customized_name}.dir field as the subdirectory of the persistent volume in the Pod /var/lib/dm-worker directory. For example, /var/lib/dm-worker/dumped_data.
      • Reference ${customized_name} in the instance configuration. For example, .

    Refer to the corresponding steps in and fill in the master-addr as ${dm_cluster_name}-dm-master:8261.