No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionInsight HD 6.5.0 Software Installation 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Installing a Client

Installing a Client

Scenario

Install the clients of all services (except Flume). FusionInsight HD provides shell scripts for different services for maintenance personnel to log in to related maintenance clients and implement maintenance operations.

NOTE:
  • Reinstall the client after server configuration is modified on the Manager portal or after the system is upgraded. Otherwise, the versions of the client and server will be inconsistent.
  • If the Flume client needs to be installed, see Service Operation Guide.
  • OpenJDK1.8.0_161 is recommended in ARM version.

Prerequisites

  • The client installation directory is automatically created if it does not exist. If it already exists, it must be empty. The directory cannot contain any space.
  • If the node where the client is to be installed is a server outside the cluster, it must be able to communicate with the service plane. Otherwise, the client will fail to be installed.
  • The client must be enabled with the NTP service and synchronize time with the server. Otherwise, the client will fail to be installed.
  • The HDFS and MapReduce components are stored in the same directory (client directory/HDFS/) after being downloaded.
  • You can install or use the client as any user. Obtain the username and password from the administrator. This section uses user user_client as an example. User user_client is the owner of the server file directory (such as /opt/client) and the client installation directory (such as /opt/hadoopclient) with the permissions of 755.
  • You have obtained the component service user (default user or new user) and password.

Procedure

  1. Obtain the software package.

    Log in to FusionInsight Manager. Choose Homepage > More > Download Client. The Download Cluster Client window is displayed.
    Figure 5-2 Download cluster client
    NOTE:

    In a single-client scenario, choose Cluster > Service > service name > More > Download Client. The Download Client dialog box is displayed.

  2. Set Select Client type to Complete Client.

    Configuration Files Only is to download client configuration files in the following scenario: After all clients are downloaded and installed and administrators modify server configuration on the Manager portal, development personnel need to update the configuration files during application development.

    There are two client software packages:

    • x86_64: client software package that can be deployed on the x86 platform, which is selected by default for the x86 cluster. By default, it is not used for the ARM cluster. To use it for the ARM cluster, register the x86 software package with the ARM cluster by following the instructions in Software Installation > Initial Configuration > Registering Software Packages for Cross-Platform (x86 and ARM) Clusters.
    • aarch64: client software package that can be deployed on the ARM platform, which is selected by default for the ARM cluster. By default, it is not used for the X86 cluster. To use it for the x86 cluster, register the ARM software package with the x86 cluster by following the instructions in Software Installation > Initial Configuration > Registering Software Packages for Cross-Platform (x86 and ARM) Clusters.

  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. The directory can be customized and user omm has the read, write, and execute permission on the directory. Click OK, copy software package FusionInsight_Services_Client.tar to the file directory, for example, /opt/client, on the server where the client is to be installed as user omm or root. Then, go to Step 5.
      NOTE:

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

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

  4. Upload the software package. Use WinSCP to upload the software package FusionInsight_Services_Client.tar to the server file directory where the client is to be installed (such as /opt/client) as the user who is to install the client (any user, such as user user_client).

    NOTE:
    • The host where the client is to be installed can be a node in the cluster or outside the cluster. If the node is a server outside the cluster, it must be able to communicate with the service plane, and the NTP service must be enabled to ensure that the time is the same as that on the server.
    • For example, you can configure NTP clock sources for external client servers as well as clusters. Then you can execute the ntpq -np command to check whether the time is synchronized.
      • If there is a * before the result of the NTP clock source IP address, it means time synchronization is normal, as follows:
        remote refid st t when poll reach delay offset jitter 
        ============================================================================== 
        *10.10.10.162 .LOCL. 1 u 1 16 377 0.270 -1.562 0.014
      • If there is no * before the result of the NTP clock source IP address, and the result of refid is .INIT., or the results showed abnormal, it means synchronization is exception, please contact technical support.
        remote refid st t when poll reach delay offset jitter 
        ============================================================================== 
        10.10.10.162 .INIT. 1 u 1 16 377 0.270 -1.562 0.014

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

    Go to the directory where the package is stored, for example, /opt/client. Run the following command to decompress the package to a local directory:

    tar -xvf FusionInsight_Services_Client.tar

  7. Verify the software package.

    Run the sha256sum to verify the retrieved file, for example,

    sha256sum -c FusionInsight_Services_ClientConfig.tar.sha256

    FusionInsight_Services_ClientConfig.tar: OK

  8. Run the following command to decompress the retrieved file:

    tar -xvf FusionInsight_Services_ClientConfig.tar

  9. Configure network connections for the client.

    1. Ensure that the host where the client is installed can communicate with the hosts listed in the hosts file stored in the directory containing the decompressed package, for example, /opt/client/FusionInsight_Services_ClientConfig/hosts.
    2. If the host where the client is installed is not a host in the cluster, you need to set the mapping between the host name and the service plane IP address for each cluster node in /etc/hosts, user root rights are required to modify the file. Each host name uniquely maps an IP address.
    NOTE:
    • If the host where the client is installed is not a host in the cluster, configure network connections for the client to prevent errors from occurring when you run commands on the client.
    • If the Spark task is run in yarn-client mode, add the spark.driver.host parameter in the Client installation directory/Spark/spark/conf/spark-defaults.conf file and set the parameter value to the IP address of the client.
    • When yarn-client mode is used, to ensure that the Spark WebUI can properly display information, add the mappings between the client IP addresses and host names to the hosts file on the active and standby Yarn nodes, that is, the ResourceManager nodes in the cluster.

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

    cd /opt/client/FusionInsight_Services_ClientConfig

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

    Components client installation is complete.
    NOTE:
    • If the /opt/hadoopclient directory has been used by the client of all or some installed services, use another directory when another client is installed.
    • Delete the client installation directory to uninstall the client.
    • To ensure that the client you install can only be used by you, add the -o parameter. That is, run the ./install.sh /opt/hadoopclient -o command to install the client.

  11. Log in to the client to check whether the client is successfully installed.

    1. Run the cd /opt/hadoopclient command to go to the client installation directory.
    2. Run the source bigdata_env command to configure the environment variables for the client.
    3. Run the following command to set kinit authentication and enter the password for logging in to the client:

      kinit admin

      Password for admin@HADOOP.COM:          #Enter the login password of user admin (this password is the same as the user password for cluster login).
    4. Run the klist command to view and confirm authentication details.
      Ticket cache: FILE:/tmp/krb5cc_0 
        Default principal: admin@HADOOP.COM 
       
        Valid starting     Expires            Service principal 
        04/09/13 18:22:35  04/10/13 18:22:29  krbtgt/HADOOP.COM@HADOOP.COM
      NOTE:
      • When kinit authentication is used, the ticket is stored in the /tmp/krb5cc_uid directory by default.

        uid indicates the ID of the user who logs in to the operating system. For example, if the UID of user root is 0, the ticket generated for kinit authentication after user root logs in to the system is stored in the /tmp/krb5cc_0 directory.

      • If kinit authentication is used and the same user is used to log in to the operating system, there is a risk that tickets are overwritten. You can set the -c cache_name parameter to specify the ticket buffer location or set the KRB5CCNAME environment variable to avoid this problem.

  12. After the cluster is reinstalled, the client that has been installed is no longer available. Perform the following operations to reinstall the client.

    1. Use PuTTY to log in to the node where the client is located as user root.
    2. Run the following command to check the directory where the client is located. (In the following example, the client is located in the /opt/hadoopclient directory.)

      ll /opt

       
      drwxr-x---. 5 root root       4096 Dec  6 01:27 FusionInsight 
      drwxr-x---. 6 root root       4096 Nov 20 00:00 FusionInsight_Services_ClientConfig 
      drwxr-x---. 6 root root       4096 Dec 11 19:00 hadoopclient 
      drwxr-xr-x. 3 root root       4096 Dec  9 02:04 huawei 
      drwx------. 2 root root  16384 Nov  6 01:03 lost+found 
      drwxr-xr-x. 2 root root       4096 Nov  7 09:49 rh 
           
    3. Run the rm -rf command to delete the directory where the client program is located and all files in this directory. (For example, delete the /opt/hadoopclient directory and all files in it.)

      rm -rf /opt/hadoopclient

    4. Reinstall the client.

Download
Updated: 2019-05-17

Document ID: EDOC1100074555

Views: 6001

Downloads: 6

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next