How Do I Replace Packages When I Create a Verification Task for an MRS 3.1.0 Cluster Using Yarn?

Scenarios

The following describes how to replace packages when you create a full or selective verification task for an HBase cluster that uses Yarn mode.

Procedure

1. On the server where the MgC Agent is installed, run the following command to access the specified MgC Agent directory:

   cd /opt/cloud/MgC-Agent/tools/plugins/collectors/bigdata-migration/hadoop3

2. Run the following command to delete the old packages from the directory:

   rm -f hadoop-c* hadoop-m*  hadoop-y* zookeeper-* hbase-* hadoop-h*

3. Go to the lib directory of the HBase client in the cluster and run the following command to copy the new packages to the specified directory: Replace xxxx@xxx.xx.xx.xx with the username and IP address of the server with the MgC Agent installed.

   scp hadoop-c* hadoop-m*  hadoop-y* zookeeper-* hbase-* opentracing-* jaeger-core-* commons-validator* hadoop-h* xxxx@xxx.xx.xx.xx:/opt/cloud/MgC-Agent/tools/plugins/collectors/bigdata-migration/hadoop3

4. Go to the specified directory on the server with the MgC Agent installed by referring to step 1. Run the following command to change the permissions and owner for the new packages:

   chmod 755 hadoop-c* hadoop-m* hadoop-y* zookeeper-* hbase-* opentracing-* jaeger-core-* commons-validator* hadoop-h*
   chown mgcagent:mgcagentgroup hadoop-c* hadoop-m* hadoop-y* zookeeper-* hbase-* opentracing-* jaeger-core-* commons-validator* hadoop-h*

5. Restart the MgC Agent.

   cd /opt/cloud/MgC-Agent/scripts
   sh start.sh