Batch Upgrading MRS Cluster Clients

The client package downloaded from FusionInsight Manager contains the client batch upgrade tool. When multiple clients need to be upgraded after the cluster upgrade or scale-out, you can use this tool to upgrade the clients in batches with a few clicks. In addition to upgrading clients in batches, this tool also provides the lightweight function of updating the /etc/hosts files on the nodes where the clients are located in batches.

Notes and Constraints

This section applies only to MRS 3.x or later.

Preparing for the Batch Upgrade

Log in to FusionInsight Manager of the MRS cluster.

For details about how to log in to FusionInsight Manager, see Accessing MRS Manager.
Choose Cluster > Overview > More > Download Client (for MRS 3.3.0 or later, click Download Client on the Homepage page) to download the client to a specified directory on the server.

For details, see Installing an MRS Cluster Client.

Decompress the downloaded client package and find the batch_upgrade directory, for example, /tmp/FusionInsight-Client/FusionInsight_Cluster_1_Services_ClientConfig/batch_upgrade.
Choose Cluster > Client Management. On the Client Management page, click Export All to export all client information to the local PC.
Decompress the exported client information and upload the client-info.cfg file to the batch_upgrade directory.
Perform the following operations to supplement the missing passwords in the client-info.cfg file:

Run the following command to add a user password:
```
vi client-info.cfg
```
Example:
```
clientIp,clientPath,user,password
10.10.10.100,/home/omm/client /home/omm/client2,omm,Password
```
The fields in the configuration file are as follows:
- clientIp: indicates the IP address of the node where the client is located.
- clientPath: indicates the client installation path. Multiple paths are separated by spaces. Note that the path cannot end with a slash (/).
- user: indicates the username of the node.
- password: indicates the user password of the node.
If the execution fails, view the node.log file in the work_space/log_XXX directory.

Configuration files containing authentication passwords pose security risks. Delete such files after configuration or store them securely.

Procedure

Perform the upgrade.

sh client_batch_upgrade.sh -u -f /tmp/FusionInsight-Client/FusionInsight_Cluster_1_Services_Client.tar -g /tmp/FusionInsight-Client/FusionInsight_Cluster_1_Services_ClientConfig/batch_upgrade/client-info.cfg

You are advised to delete the client-info.cfg file as soon as possible after the upgrade because the password has been configured.

After the upgrade is complete, verify the upgrade result by running the following command:
```
sh client_batch_upgrade.sh -c
```
If the client does not function properly after the upgrade, run the following command to roll back the client:
```
sh client_batch_upgrade.sh -s
```
- The client batch upgrade tool moves the original client to the backup directory, and then installs the client using the package specified by the -f parameter. Therefore, if the original client contains customized content, manually save the customized content from the backup directory or move it to the client directory after the upgrade, before running the -c command.
  The backup path on the client is {Original client path}-backup.
- The -u command is the prerequisite for the -c and -s commands. You can run the -c command to commit the upgrade or the -s command to perform a rollback only after the -u command is executed to perform an upgrade.
- You can execute the -u command multiple times. Each execution upgrades only the clients that failed previously, while successfully upgraded clients are skipped.
- The client batch upgrade tool also supports the clients of earlier versions.
- When upgrading a client installed by a non-root user, ensure that the user has the read and write permissions on both the client directory and its parent directory on the target node. Otherwise, the upgrade will fail.
- The client package specified by the -f parameter must be a full client package. Client packages containing only a single component or a subset of components cannot be used as input.

Updating the hosts Files in Batches

Complete all preparations by referring to Preparing for the Batch Upgrade.
Check whether the user configured for the node where the /etc/hosts files need to be updated is root.
- If yes, go to Step 3.
- If no, change the user to root and go to Step 3.
Update the /etc/hosts files on the nodes where the client is located in batches.
```
sh client_batch_upgrade.sh -r -f /tmp/FusionInsight-Client/FusionInsight_Cluster_1_Services_Client.tar -g /tmp/FusionInsight-Client/FusionInsight_Cluster_1_Services_ClientConfig/batch_upgrade/client-info.cfg
```
- When you batch update the /etc/hosts files, the specified client package can be either a complete client package or a package containing only configuration files (recommended).
- The user configured for the host where the /etc/hosts files need to be updated must be root. Otherwise, the update fails.