Help Center > > User Guide> Using an MRS Client> Installing a Client> Installing a Client (Version 3.x or Later)

Installing a Client (Version 3.x or Later)

Updated at: Oct 21, 2021 GMT+08:00

Scenario

This section describes how to install clients of all services (excluding Flume) in an MRS cluster. For details about how to install the Flume client, see Installing the Flume Client.

A client can be installed on a node inside or outside the cluster. This section uses the installation directory /opt/hadoopclient as an example. Replace it to the actual one.

Prerequisites

  • A Linux 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

    Euler

    Euler OS 2.5

    SuSE

    SUSE Linux Enterprise Server 12 SP4 (SUSE 12.4)

    RedHat

    Red Hat-7.5-x86_64 (Red Hat 7.5)

    CentOS

    CentOS-7.6

    Kunpeng computing (Arm)

    Euler

    Euler OS 2.8

    CentOS

    CentOS-7.6

    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 must be the same as that of the master node in an MRS cluster.
  • The NTP service has been installed on the ECS OS and is running properly.

    If the NTP service is not installed, run the yum install ntp -y command to install it when the yum source is configured.

  • A user can log in to the Linux ECS using the password (in SSH mode).

Installing a Client on a Node Inside a Cluster

  1. Obtain the software package.

    Log in to FusionInsight Manager. For details, see Accessing FusionInsight Manager (MRS 3.x or Later). Click the name of the cluster to be operated in the Cluster drop-down list.

    Choose More > Download Client. The Download Cluster Client dialog box is displayed.
    Figure 1 Downloading a client

    In the scenario where only one client is to be installed, choose Cluster > Service > Service name > More > Download Client. The Download Client dialog box is displayed.

  2. Set the client type to Complete Client.

    Configuration Files Only is to download client configuration files in the following scenario: After a complete client is downloaded and installed and administrators modify server configurations on Manager, developers need to update the configuration files during application development.

    The platform type can be set to x86_64 or aarch64.

    • x86_64: indicates the client software package that can be deployed on the x86 platform.
    • aarch64: indicates the client software package that can be deployed on the TaiShan servers.

    The cluster supports two types of clients: x86_64 and aarch64. The client type must match the architecture of the node to be installed. Otherwise, client installation will fail.

  3. Determine whether to generate a client 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. Click OK and copy the software package to the file directory, for example, /opt/Bigdata/client, on the server where the client is to be installed as user omm or root. Then go to 5.

      If you cannot obtain permissions of user root, use user omm.

    • If no, click OK, specify a local save path, and download the complete client. Wait until the download is complete and go to 4.
  4. Upload the software package.

    Use WinSCP to upload the obtained software package as the user (such as user_client) who prepares for the installation, to the directory (such as /opt/Bigdata/client) of the server where the client is to be installed.

    The format of the client software package name is as follows: FusionInsight_Cluster_<Cluster ID>_Services_Client.tar.

    The following steps and sections use FusionInsight_Cluster_1_Services_Client.tar as an example.

  5. Log in to the server where the client software package is located as user user_client.
  6. Decompress the software package.

    Go to the directory where the installation package is stored, such as /opt/Bigdata/client. Run the following command to decompress the installation package to a local directory:

    tar -xvf FusionInsight_Cluster_1_Services_Client.tar

  7. 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.tar.sha256

    FusionInsight_Cluster_1_Services_Client.tar: OK     
  8. Decompress the obtained installation file.

    tar -xvf FusionInsight_Cluster_1_Services_ClientConfig.tar

  9. Go to the directory where the installation package is stored, and run the following command to install the client to a specified directory (an absolute path), for example, /opt/hadoopclient:

    cd /opt/Bigdata/client/FusionInsight_Cluster_1_Services_ClientConfig

    Run the ./install.sh /opt/hadoopclient command to install the client. The client is successfully installed if information similar to the following is displayed:

    The component client is installed successfully
    • If the clients of all or some services use the /opt/hadoopclient directory, other directories must be used when you install other service clients.
    • You must delete the client installation directory when uninstalling a client.
    • To ensure that an installed client can only be used by the installation user (for example, user_client), add parameter -o during the installation. That is, run the ./install.sh /opt/hadoopclient -o command to install the client.
    • If an HBase client is installed, it is recommended that the client installation directory contain only uppercase and lowercase letters, digits, and characters (_-?.@+=) due to the limitation of the Ruby syntax used by HBase.

Using a Client

  1. 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/hadoopclient

  2. Run the following command to configure environment variables:

    source bigdata_env

  3. 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.

  4. 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 a Cluster

  1. Create an ECS that meets the requirements in the prerequisites.
  2. Perform NTP time synchronization to synchronize the time of nodes outside the cluster with the time of the MRS cluster.
    1. Run the vi /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 profer
      server master2_ip 
      Figure 2 Adding the master node IP addresses
    2. Run the service ntpd stop command to stop the NTP service.
    3. Run the /usr/sbin/ntpdate IP address of the active master node command to manually synchronize the time.
    4. Run the service ntpd start or systemctl restart ntpd command to start the NTP service.
    5. Run the ntpstat command to check the time synchronization result.
  3. Perform the following steps to download the cluster client software package from FusionInsight Manager, copy the package to the ECS node, and install the client:
    1. Access FusionInsight Manager and download the cluster client to the specified directory on the active management node by referring to Accessing FusionInsight Manager (MRS 3.x or Later) and Installing a Client on a Node Inside a Cluster, respectively.
    2. Log in to the active management node as user root.

      sudo su - omm

    3. Run the following command to copy the client to the node where the client is to be installed:

      scp -p /tmp/FusionInsight-Client/FusionInsight_Cluster_1_Services_Client.tar IP address of the node where the client is to be installed:/tmp

    4. Log in to a node on which the client is to be installed as the client user.

      Run the following command to install the client. If you do not have the file operation permission, change the file permission as user root.

      cd /tmp

      tar -xvf FusionInsight_Cluster_1_Services_Client.tar

      tar -xvf FusionInsight_Cluster_1_Services_ClientConfig.tar

      cd /tmp/FusionInsight_Cluster_1_Services_ClientConfig

      ./install.sh /opt/mrsclient

    5. Run the following commands to switch to the client directory and configure environment variables:

      cd /opt/mrsclient

      source bigdata_env

    6. 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

    7. Run the client command of a component directly.

      For example, run the hdfs dfs -ls / command to view files in the HDFS root directory.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel