Installing a Client (Versions Earlier Than 3.x)

Scenario

An MRS client is required. The MRS cluster client can be installed on the Master or Core node in the cluster or on a node outside the cluster.

After a cluster of versions earlier than MRS 3.x is created, a client is installed on the active Master node by default. You can directly use the client. The installation directory is /opt/client.

For details about how to install a client of MRS 3.x or later, see Installing a Client (MRS 3.x or Later).

If a client has been installed on the node outside the MRS cluster and the client only needs to be updated, update the client using the user who installed the client, for example, user root.

Installing a Client on the Core Node

Log in to MRS Manager and choose Services > Download Client to download the client installation package to the active management node.

If only the client configuration file needs to be updated, see method 2 in Updating a Client (Versions Earlier Than 3.x).
Use the IP address to search for the active management node, and log in to the active management node using VNC.
Log in to the active management node, and run the following command to switch the user:
sudo su - omm
On the MRS management console, view the IP address on the Nodes tab page of the specified cluster.
Record the IP address of the Core node where the client is to be used.
On the active management node, run the following command to copy the client installation package to the Core node:
scp -p /tmp/MRS-client/MRS_Services_Client.tar IP address of the Core node:/opt/client
Log in to the Core node as user root.
Master nodes support Cloud-Init. The preset username for Cloud-Init is root and the password is the one you set during cluster creation.
Run the following commands to install the client:
cd /opt/client

tar -xvf MRS_Services_Client.tar

tar -xvf MRS_Services_ClientConfig.tar

cd /opt/client/MRS_Services_ClientConfig

./install.sh Client installation directory

For example, run the following command:

./install.sh /opt/client
For details about how to use the client, see Using an MRS Client.

Using an MRS Client

On the node where the client is installed, run the sudo su - omm command to switch the user. Run the following command to go to the client directory:
cd /opt/client
Run the following command to configure environment variables:
source bigdata_env
If Kerberos authentication is enabled for the current cluster, run the following command to authenticate the user. If Kerberos authentication is disabled for the current cluster, skip this step.
kinit MRS cluster user

Example: kinit admin

User admin is created by default for MRS clusters with Kerberos authentication enabled and is used for administrators to maintain the clusters.
Run the client command of a component directly.
For example, run the hdfs dfs -ls / command to view files in the HDFS root directory.

Installing a Client on a Node Outside the Cluster

Create an ECS that meets the following requirements:

For clusters of versions earlier than MRS 3.x, you need to confirm the CPU architecture of the current MRS cluster nodes. For clusters of versions earlier than MRS 3.x, the CPU architecture of the ECS must be the same as that of the MRS cluster node. For MRS 3.x or later, the MRS client is compatible with both of the following CPU architectures.

An ECS has been prepared. For details about the OS and its version of the ECS, see Table 1.

**Table 1** Reference list
CPU Architecture	OS	Supported Version
x86 computing	EulerOS	Available: EulerOS 2.2 Available: EulerOS 2.3 Available: EulerOS 2.5

For example, a user can select an ECS running the EulerOS.

In addition, sufficient disk space is allocated for the ECS, for example, 40 GB.

The ECS and the MRS cluster are in the same VPC.
The security group of the ECS is the same as that of the master node in the MRS cluster.
If this requirement is not met, modify the ECS security group or configure the inbound and outbound rules of the ECS security group to allow the ECS security group to be accessed by all security groups of MRS cluster nodes.
To enable users to log in to a Linux ECS using a password (SSH), see "Instances" > "Logging In to a Linux ECS" > "Login Using an SSH Password" in Elastic Cloud Server User Guide.
All ports in the inbound direction of the MRS cluster security group are open to the client node. For details, see Adding a Security Group Rule.

Log in to MRS Manager. For details, see Accessing MRS Manager (Versions Earlier Than MRS 3.x). Then, choose Services.
Click Download Client.
In Client Type, select All client files.
In Download To, select Remote host.
Set Host IP Address to the IP address of the ECS, Host Port to 22, and Save Path to /tmp.
- If the default port 22 for logging in to an ECS using SSH has been changed, set Host Port to the new port.
- Save Path contains a maximum of 256 characters.
Set Login User to root.

If other users are used, ensure that the users have read, write, and execute permission on the save path.
Select Password or SSH Private Key for Login Mode.
- Password: Enter the password of user root set during cluster creation.
- SSH Private Key: Select and upload the key file used for creating the cluster.
Click OK to generate a client file.

If the following information is displayed, the client package is saved. Click Close. Obtain the client file from the save path on the remote host that is set when the client is downloaded.
```
Client files downloaded to the remote host successfully.
```
If the following information is displayed, check the username, password, and security group configurations of the remote host. Ensure that the username and password are correct and an inbound rule of the SSH (22) port has been added to the security group of the remote host. And then, go to 2 to download the client again.
```
Failed to connect to the server. Please check the network connection or parameter settings.
```
Generating a client will occupy a large number of disk I/Os. You are advised not to download a client when the cluster is being installed, started, and patched, or in other unstable states.
Log in to the ECS using VNC. For details, see Instance > Logging In to a Linux > Logging In to a Linux in the Elastic Cloud Server User Guide

All images support Cloud-Init. The preset username for Cloud-Init is root and the password is the one you set during cluster creation. It is recommended that you change the password upon the first login.
Perform NTP time synchronization to synchronize the time of nodes outside the cluster with the time of the MRS cluster.
1. Check whether the NTP service is installed. If it is not installed, run the yum install ntp -y command to install it.
2. Run the vim /etc/ntp.conf command to edit the NTP client configuration file, add the IP address of the Master node in the MRS cluster, and comment out the IP addresses of other servers.
```
server master1_ip prefer
server master2_ip 
```
  Figure 1 Adding the master node IP addresses
3. Run the service ntpd stop command to stop the NTP service.
4. Run the following command to manually synchronize the time:
  /usr/sbin/ntpdate 192.168.10.8
  
  192.168.10.8 indicates the IP address of the active Master node.
5. Run the service ntpd start or systemctl restart ntpd command to start the NTP service.
6. Run the ntpstat command to check the time synchronization result:
On the ECS, switch to user root and copy the installation package in Save Path in 6 to the /opt directory. For example, if Save Path is set to /tmp, run the following commands:

sudo su - root

cp /tmp/MRS_Services_Client.tar /opt
Run the following command in the /opt directory to decompress the package and obtain the verification file and the configuration package of the client:

tar -xvf MRS_Services_Client.tar
Run the following command to verify the configuration file package of the client:

sha256sum -c MRS_Services_ClientConfig.tar.sha256

The command output is as follows:
```
MRS_Services_ClientConfig.tar: OK
```
Run the following command to decompress MRS_Services_ClientConfig.tar:

tar -xvf MRS_Services_ClientConfig.tar
Run the following command to install the client to a new directory, for example, /opt/Bigdata/client. A directory is automatically generated during the client installation.

sh /opt/MRS_Services_ClientConfig/install.sh /opt/Bigdata/client

If the following information is displayed, the client has been successfully installed:
```
Components client installation is complete.
```
Check whether the IP address of the ECS node is connected to the IP address of the cluster Master node.

For example, run the following command: ping Master node IP address.
- If yes, go to 18.
- If no, check whether the VPC and security group are correct and whether the ECS and the MRS cluster are in the same VPC and security group, and go to 18.
Run the following command to configure environment variables:

source /opt/Bigdata/client/bigdata_env
If Kerberos authentication is enabled for the current cluster, run the following command to authenticate the user. If Kerberos authentication is disabled for the current cluster, skip this step.

kinit MRS cluster user

Example: kinit admin
Run the client command of a component.

For example, run the following command to query the HDFS directory:

hdfs dfs -ls /