Verifying the Consistency of Data Migrated Between MRS HBase Clusters

This section describes how to use MgC to verify the consistency of data migrated between different versions of Huawei Cloud MRS HBase clusters.

Preparations

Install Edge, an MgC tool used for data verification, in the source intranet environment and register an account for using Edge. For details, see Installing Edge for Linux.
Add the mappings between the hostnames and IP addresses of all nodes in the source and target clusters to the /etc/hosts file on the server where Edge is installed.
1. On the server where Edge is installed, open the /etc/hosts file.
2. In the /etc/hosts file, add a line for each node in the source and target clusters in the following format:
```
IP address Hostname
```
  For example, if a node uses the IP address 192.168.1.1 and has the hostname source-node-01, add the following information:
```
192.168.1.1 source-node-01
```
3. After all mappings are added, save and close the /etc/hosts file.
4. Ping a hostname to check whether it can be resolved successfully. For example:
```
ping source-node-01
```

Procedure

Sign in to the MgC console. On the Overview page, click Create Migration Project.
In the displayed dialog box, enter a project name, select a project type, and click Confirm.

To review this migration project, choose Settings > Migration Projects in the navigation pane.
Connect Edge to MgC. For more information, see Connecting the Edge Device to MgC.
After the connection is successful, add the username/key pairs for accessing the source and target MRS HBase clusters to Edge. For more information, see Adding Resource Credentials. Enter the username for logging in to the HBase client in the Username box and upload the configuration files for Key:
- For an unsecured cluster (with Kerberos authentication disabled), you need to upload five configuration files: core-site.xml, hdfs-site.xml, yarn-site.xml, mapred-site.xml, and hbase-site.xml. For details about how to obtain the configuration files, see Preparing the Configuration Files of the Running Environment. Review whether Kerberos authentication is enabled for the cluster in the basic cluster information.
- For a secured cluster (with Kerberos authentication enabled), upload seven files: core-site.xml, hdfs-site.xml, yarn-site.xml, krb5.conf, user.keytab, mapred-site.xml, and hbase-site.xml. The krb5.conf and user.keytab files contain the credentials of the cluster users. You can perform the following steps to obtain the two files. For details about how to obtain the other five configuration files, see Preparing the Configuration Files of the Running Environment.
  1. Log in to FusionInsight Manager, and choose System > Permission > User.
  2. Select developuser and choose More > Download Authentication Credential to download the authentication credential files.
  3. Decompress the downloaded file to obtain the user.keytab and krb5.conf files.
On the MgC console, in the navigation pane on the left, choose Research > Data Lineage. In the upper left corner of the page, choose the migration project created in step 2.
In the Metadata Collection area, click Create Connection.
On the Select Connection Type page, select HBase and click Next.

Set connection parameters based on Table 1 and click Test. If the test is successful, the connection is set up.

**Table 1** Parameters for creating an HBase connection
Parameter	Configuration
Connection To	Select Source.
Connection Name	The default name is HBase-4 random characters (including letters and numbers). You can also customize a name.
Edge Device	Select the Edge device connected to MgC in step 3.
HBase Credential	Select the credential used for accessing the source MRS HBase cluster you added to Edge in step 4.
Secured Cluster	Choose whether the cluster is secured.
ZooKeeper IP Address	Enter the IP address for connecting to the ZooKeeper node. You can enter the public or private IP address of the ZooKeeper node.
ZooKeeper Port	Enter the port for connecting to the ZooKeeper node.
HBase Version	Select the HBase version.

In the Metadata Collection area, choose Create Task > Metadata Collection.

Configure the parameters for creating a metadata collection task and click Confirm.

**Table 2** Parameters for configuring a metadata collection task
Parameter	Configuration
Task Name	The default name is Metadata-Collection-4 random characters (including letters and numbers). You can also specify a name.
Metadata Connection	Select the connection created in step 8.
Databases (Optional)	Enter the names of the databases whose metadata needs to be collected. Use commas (,) to separate the database names. If no database name is specified, the metadata of all databases is collected.
Concurrent Threads	Set the maximum number of threads for executing the collection. The default value is 3. The value ranges from 1 to 10. More concurrent threads means more efficient collection, but more connection and Edge device resources will be consumed.

In the Metadata Collection area, click Collection tasks.
Under Tasks, you can review the created metadata collection task and its settings. Click Execute Task in the Operation column to run the task. Each time the task is executed, a task execution is generated.
Click View Executions in the Operation column. Under Task Executions, you can view the execution records of the task and the status and collection results of each task execution. When a task execution enters a Completed status and the collection results are displayed, you can view the list of databases and tables extracted from collected metadata on the Tables tab.
In the navigation pane on the left, choose Migrate > Big Data Verification. If this is your first time to visit this page, select an Edge device to enable the verification feature. Click Select Edge Device. In the displayed dialog box, select the Edge device connected to MgC in step 3.

Ensure that the selected Edge device is always Online and Enabled before your verification is complete.
In the Features area, click Table Management.

Under Table Groups, click Create. Configure the parameters for creating a table group and click Confirm.

**Table 3** Parameters for creating a table group
Parameter	Description
Table Group	Enter a name.
Metadata Connection	Select the connection created in step 8. CAUTION: A table group can only contain tables coming from the same metadata source.
Verification Rule	Select a rule that defines the method for verifying data consistency and the inconsistency tolerance. You can View More to see the details about the verification rules provided by MgC.
Description (Optional)	Enter a description to identify the table group.

On the Table Management page, click the Tables tab, select the data tables to be added to the same table group, and choose Option > Add Tables to Group above the list. In the displayed dialog box, select the desired table group and click Confirm.

You can manually import information of incremental data tables to MgC. For details, see Creating a Table Group and Adding Tables to the Group.
On the Big Data Verification page, in the Features area, click Connection Management.
Click Create Connection in the upper right corner of the page. On the Select Connection Type page, select HBase and click Next.

Set connection parameters based on Table 4 and click Test. If the test is successful, the connection is set up.

**Table 4** Parameters for creating an HBase connection
Parameter	Configuration
Connection To	Select Target.
Connection Name	The default name is HBase-4 random characters (including letters and numbers). You can also customize a name.
HBase Credential	Select the credential used for accessing the target MRS HBase cluster you added to Edge in step 4.
Secured Cluster	Choose whether the cluster is secured.
ZooKeeper IP Address	Enter the IP address for connecting to the ZooKeeper node. You can enter the public or private IP address of the ZooKeeper node.
ZooKeeper Port	Enter the port for connecting to the ZooKeeper node. The default value is 2181.
HBase Version	Select the HBase version.

On the MgC console, create a verification task for the source and target HBase clusters, respectively, and execute the tasks. For details, see Creating and Executing Verification Tasks. During the task creation, select the table group created in step 16.
- On the Select Task Type page, choose HBase.
- Select a verification method. For details about each verification method, see Verification Methods.
Wait until the task executions enter a Completed status. You can view and export the task execution results on the Verification Results page. For details, see Viewing and Exporting Verification Results.