Updating the MRS Cluster Client After the Server Configuration Expires

Updating Client Configurations (Version 3.x or Later)

MRS 3.x and later versions support three methods for updating client configurations. Choose the method that best fits your environment.

Method 1

1. Log in to MRS Manager and choose Cluster > Dashboard > More > Download Client. For MRS 3.3.0 or later, click Download Client on the Homepage page.

   For details about how to log in to MRS Manager, see Accessing MRS Manager.

2. Choose More > Download Client > Configuration Files Only.

   The generated compressed file contains the configuration files of all services.

   Figure 1 Downloading the client configuration file
   

3. Set the parameters.

   For versions earlier than MRS 3.3.1:

   Determine whether to generate a configuration file on the cluster node.

   • If yes, select Save to Path, and click OK to generate the client file. By default, the client file is generated in /tmp/FusionInsight-Client on the active management node. You can also store the client file in other directories, and user omm has the read, write, and execute permissions on the directories. Then go to Step 4.
   • If no, click OK, specify a local save path, and download the complete client. Wait until the download is complete and go to Step 4.
   For MRS 3.3.1 and later versions:

   1. Set the Select Download Location parameter as needed.
      • Server: Download the file to the active OMS node of the cluster.
      • Browser: Download the file to the local computer.
      • Remote Node: Download the file to a node other than the active OMS node.
   2. Set Save to Path as prompted. If you select Browser as the download location, leave this parameter blank.
   3. If you select Remote Node, configure the required parameters by referring to Table 1.

      Table 1 Parameters for downloading to a remote node

      Parameter	Description	Example Value
      Host IP Address	IP address of the remote node. The platform type of the remote node must be the same as that of the downloaded client. Otherwise, the client may fail to be installed.	x.x.x.x
      Host Port	Host port of the remote node.	22
      Username	Username for logging in to the remote node. The user must have the write permission for the path.	xxx
      Authentication Method	You can choose one of the following methods: Password: Use the password for login. SSH private keys: Use SSH private keys for login. None: To use this method, passwordless login needs to be enabled.	Password
      Password	Enter the password when Authentication Method is set to Password. Password for logging in to the remote node.	xxx
      SSH private keys	This parameter is mandatory when Authentication Method is set to SSH private keys. Click Add and select the SSH private key file to upload.	-
      Auto Deployment	Whether to enable auto deployment. This parameter is mandatory when Select Client Type is set to Complete Client. If you set this parameter to yes, the client is automatically installed and deployed on the current node. If you set this parameter to no, the client will not be automatically installed and deployed. You need to manually install the client after it is downloaded.	Yes
      Deployment Path	This parameter is mandatory when Auto Deployment is set to Yes. If only the configuration file is downloaded, this parameter will not be displayed. The deployment path must be empty if it already exists on the remote node. Otherwise, it will be created automatically. This path also requires execute and write permissions.	/opt/testclient

4. Use WinSCP to save the compressed file to the client installation directory, for example, /opt/hadoopclient, as the client installation user.
5. Decompress the software package.

   Run the following commands to go to the directory where the client is installed, and decompress the file to a local directory. For example, the downloaded client file is FusionInsight_Cluster_1_Services_Client.tar.

   cd /opt/hadoopclient

   tar -xvf FusionInsight_Cluster_1_Services_Client.tar

6. Verify the software package.

   Run the following command to verify the decompressed file and check whether the command output is consistent with the information in the sha256 file.

   sha256sum -c FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles.tar.sha256

   The following information is displayed:

   FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles.tar: OK     

7. Decompress the package to obtain the configuration file.

   tar -xvf FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles.tar

8. Run the following command in the client installation directory to update the client using the configuration file:

   sh refreshConfig.sh Client installation directory Directory where the configuration file is stored

   For example, run the following command:

   sh refreshConfig.sh /opt/hadoopclient /opt/hadoopclient/FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles

   If the following information is displayed, the configurations have been updated successfully.

   Succeed to refresh components client config.

Method 2:

1. Log in to the client installation node as user root.
2. Go to the client installation directory, for example, /opt/hadoopclient and run the following commands to update the configuration file:

   cd /opt/hadoopclient

   sh autoRefreshConfig.sh

3. Enter the username and password of the FusionInsight Manager administrator and the floating IP address of OMS.

   To obtain the floating IP address of OMS, log in to the Master2 node remotely, and run the ifconfig command. In the command output, eth0:wsom indicates the floating IP address of OMS. Record the value of inet. If the floating IP address of OMS cannot be queried on the Master2 node, switch to the Master1 node to query and record the floating IP address. If there is only one Master node, query and record the IP address on the Master node.

4. Enter the names of the components whose configuration needs to be updated. Use commas (,) to separate the component names. Press Enter to update the configurations of all components if necessary.

   If the following information is displayed, the configurations have been updated successfully.

   Succeed to refresh components client config.

Method 3 (for MRS 3.3.1 and later):

1. Log in to FusionInsight Manager of the MRS cluster.

   For details about how to log in to FusionInsight Manager, see Accessing MRS Manager.

2. Choose Cluster > Client Management. On the displayed page, check whether there is the client you want to operate.
   • If yes, go to Step 3.
   • If no, click Add, configure information about the client, and click OK. Go to Step 3.

3. Click Update in the Operation column of the client you want to update.

   If you need to update clients in batches, select the target clients (use the same installation user) and choose More > Batch Update.

4. Select the checkbox for risk confirmation, configure the information in Table 2, and click OK.
   

   During a configuration update, clients may not function properly and client services may be interrupted.

   Table 2 Parameters for updating the client configuration

   Parameter	Example Value	Description
   Authentication Method	Password	You can choose one of the following methods: Password: Use the password for login. SSH private keys: Use SSH private keys for login. None: To use this method, passwordless login needs to be enabled.
   Password/SSH Private Keys	xxx	Enter the password if Authentication Method is set to Password. Upload the private key file if Authentication Method is set to SSH private keys. Click Select File and select a local file to upload.
   Host Port	22	Host port of the node where the client is to be updated
   Installation Package Path	/tmp/FusionInsight-Client/	Path for storing the installation package of the updated client If there already is a client file in the path, it will be overwritten. For a remote node, write permission for the path is required.

Verification:

On MRS Manager, choose Cluster > Client Management and check whether the client status is normal. Alternatively, run a component command (such as hdfs dfs -ls /) on the node where the client is installed. If the command runs successfully and displays no configuration expiration message, the client configuration has been updated.

Updating Client Configurations (Version 2.x or Earlier)

For MRS 2.x and earlier versions, use either of the following methods to update client configurations:

Method 1 (applicable to all versions)

1. Log in to MRS Manager and choose Services.

   For details about how to log in to MRS Manager, see Accessing MRS Manager.

2. Click Download Client.

   Set Client Type to Only configuration files, Download To to Server, and click OK to generate the client configuration file. The generated file is saved in the /tmp/MRS-client directory on the active management node by default. You can customize the file path.

   Figure 2 Downloading the client configuration file
   

3. Query and log in to the active Master node.
4. If you use the client in the cluster, run the following command to switch to user omm. If you use the client outside the cluster, switch to user root.

   sudo su - omm

5. Go to the client directory.

   cd {Client installation directory}

6. Update client configurations.

   sh refreshConfig.sh Client installation directory Full path of the client configuration file package

   Example:

   sh refreshConfig.sh /opt/Bigdata/client /tmp/MRS-client/MRS_Services_Client.tar

   If the following information is displayed, the configurations have been updated successfully.

   ReFresh components client config is complete.
   Succeed to refresh components client config.

Method 2:

1. After the cluster is installed, run the following command to switch to user omm. If you use the client outside the cluster, switch to user root.

   sudo su - omm

2. Go to the client directory.

   cd {Client installation directory}

3. Run the following command and enter the name of an MRS Manager user with the download permission and its password (for example, the username is admin and the password is the one set during cluster creation) as prompted to update client configurations.

   sh autoRefreshConfig.sh

4. After the command is executed, the following information is displayed, where XXX indicates the name of the component installed in the cluster. To update client configurations of all components, press Enter. To update client configurations of some components, enter the component names and separate them with commas (,).

   Components "xxx" have been installed in the cluster. Please input the comma-separated names of the components for which you want to update client configurations. If you press Enter without inputting any component name, the client configurations of all components will be updated:

   If the following information is displayed, the configurations have been updated:

   Succeed to refresh components client config.

   If the following information is displayed, the username or password is incorrect.

   login manager failed,Incorrect username or password.

   • This script automatically connects to the cluster and invokes the refreshConfig.sh script to download and update the client configuration file.
   • By default, the client uses the floating IP address specified by wsom=xxx in the Version file located in the installation directory to update the client configurations. To update the configuration file of another cluster, change the value of wsom=xxx in the Version file to the floating IP address of the target cluster before performing this step.

Verification:

Run a component command (such as hdfs dfs -ls /) in the client installation directory. If the command runs successfully and displays no configuration expiration message, the client configuration has been updated.

FAQs

• Why does a client configuration update fail?

  Common causes of update failures include an unreachable MRS Manager service, an incorrect OMS floating IP address, invalid MRS Manager admin credentials (username and password), or a missing refreshConfig.sh or autoRefreshConfig.sh script in the client installation directory.

  First, verify that the MRS Manager service is running normally and the OMS floating IP address is correct. When running the autoRefreshConfig.sh script, ensure you enter the correct MRS Manager administrator username and password. Next, check whether the client installation directory is complete. If the problem persists, download a complete client installation package and reinstall the client.

• What should I do if running autoRefreshConfig.sh returns an incorrect username or password error?

  The entered MRS Manager username or password is incorrect, or the user account lacks permissions to download client configuration files.

• Ensure that you enter the correct MRS Manager administrator username and password. For example, the username is admin, and the password is the one set during cluster creation. If the password has changed, use the updated password.
• What should I do if the client still reports expired configurations after an update?

  Possible causes include updating only a subset of components, which leaves unselected component configurations expired, or configuring an incorrect cluster floating IP address in the wsom=xxx parameter of the Version file in the client installation directory.

  When running autoRefreshConfig.sh, press Enter during component selection to update all component configurations. Then, verify that wsom=xxx in the Version file matches the OMS floating IP address of the current cluster.

Helpful Links

• For details about how to view an installed MRS cluster client, see Viewing the Installed MRS Cluster Client.
• For details about how to manually install an MRS cluster client, see Installing a Client (MRS 3.x).