Help Center/ Cloud Data Migration/ User Guide/ Creating and Managing a CDM Cluster/ Viewing and Modifying CDM Cluster Configurations
Updated on 2024-10-24 GMT+08:00

Viewing and Modifying CDM Cluster Configurations

Scenario

After creating a CDM cluster, you can view its basic information and modify its configurations.

  • You can view the following basic cluster information:
    • Cluster Information: cluster version, creation time, project ID, instance ID, and cluster ID
    • Instance Configuration: cluster flavor, CPU, and memory
    • Network
  • You can modify the following cluster configurations:
    • Notification: If a CDM migration job (only table/file migration) fails or the EIP is abnormal, CDM sends an SMS or email notification to the user. Notifications generated by this function will not be charged.
    • User Isolation: determines whether other users can view and operate the migration jobs and links in the cluster.
      • If this function is enabled, migration jobs and links in the cluster are isolated. Other IAM users of the a Huawei account cannot view or operate the migration jobs and links in the cluster.

        Starting jobs by group will run all jobs in the group. If user isolation is enabled, starting jobs by group will still run all jobs in the group even if otherIAM users in the a Huawei account cannot view the jobs in the group. Therefore, you are not advised to start jobs by group in user isolation scenarios.

      • If this function is disabled, migration jobs and links in the cluster can be shared with other users. All IAM users with the required permission in the a Huawei account can view and operate migration jobs and links.

        After disabling User Isolation, restart the cluster VM for the settings to take effect.

    • Maximum Concurrent Extractors: This parameter specifies the total number of concurrent extractors of a job. If the total number of concurrent extractors of all jobs exceeds the upper limit, the excess extractors will wait in a queue.

      The value of this parameter ranges from 1 to 1000. You are advised to set it based on the cluster specifications. For details about the recommended value, see Maximum Concurrent Extractors. If the number of concurrent extractors is too large, memory overflow may occur. Exercise caution when changing the value.

      This parameter is also available on the Settings tab page. You can change its value either on this page or the Settings page.

Prerequisites

You have created a CDM cluster.

Viewing Basic Cluster Information

  1. Log in to the CDM console and choose Cluster Management in the left navigation pane.

    Another method: Log in to the DataArts Studio console by following the instructions in Accessing the DataArts Studio Instance Console. On the DataArts Studio console, locate a workspace and click DataArts Migration to access the CDM console.

    Figure 1 Cluster list

    The Source column is displayed only when you access the DataArts Migration page from the DataArts Studio console.

  2. Click the cluster name to view its basic information.

Modifying Cluster Configurations

  1. Log in to the CDM console and choose Cluster Management in the left navigation pane.

    Another method: Log in to the DataArts Studio console by following the instructions in Accessing the DataArts Studio Instance Console. On the DataArts Studio console, locate a workspace and click DataArts Migration to access the CDM console.

    Figure 2 Cluster list

    The Source column is displayed only when you access the DataArts Migration page from the DataArts Studio console.

  1. Click the name of a cluster and click the Cluster Configuration tab to modify Notification, User Isolation and Maximum Concurrent Extractors.

  2. Click Save. The Cluster Management page is displayed.
  3. If User Isolation is disabled, choose More > Restart in the Operation column to restart the cluster VM for the settings to take effect.

    Figure 3 Restarting a cluster
    • Restart CDM service process: Only the CDM service process is restarted. The cluster VM will not be restarted.
    • VM restart: The service process will be interrupted and VMs in the cluster will be restarted.

  4. Select VM restart and click Yes.