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).
Configuring and Checking the Installation Environment

Configuring and Checking the Installation Environment

Scenario

To ensure stable and efficient running of FusionInsight HD, perform OS adaptation operations and check the OS before the installation. If a fault occurs during the installation, view the installation logs. For details about how to view the installation logs, see Viewing Installation Logs.

This topic provides guidance for you to complete the following operations. All operations are completed automatically by running scripts.

  • Execution of the preinstall script:
    • OS adaption: Modify the OS configuration to ensure that the OS meets FusionInsight HD installation requirements.
    • RPM supplementation: The system automatically supplements RPM packages required by the OS.
      NOTE:

      For details about the list of the RPM packages required by the FusionInsight HD system, see the corresponding OS list file in the /opt/FusionInsight_SetupTool/preinstall/script/function/add_packages/conf directory (for example, redhat-7.4_must-rpms.lst). Security risks may occur after the RPM packages are installed. When you harden the OS security, take the security risks that may be caused by installing the software that FusionInsight depends on into consideration.

    • Partition formatting: To meet the partition requirements of FusionInsight HD, the system automatically formats the disks on a server. For result, see Partition formatting results of the preinstall script.
    • After the preinstall script is executed, a statmon service is created in the OSs of all nodes to collect the OS running status. This service exists in the OS even after the cluster and Manager are uninstalled.
    • After the preinstall script is executed, a diskmgt process is created on the OSs of all nodes. This process is used to implement disk management. When a disk is faulty on a node, the tasks of this disk are automatically switched to the standby disk. This process exists on the OS even when the cluster and Manager are uninstalled. For details about the uninstallation, see How Do I Format a Disk After Successfully Running the preinstall Script?.
  • Execution of the precheck script:

    Check whether each node meets the installation requirements of FusionInsight HD. For details about the check items, see Check items of the precheck script.

Prerequisites

  • All required files have been configured and uploaded to specified locations. For details, see Generating the Configuration Files. (All files in the preinstall and precheck folders are included.)
  • If ip_forward on the management node is enabled, the management node is able to forward external network packets internally to the cluster. To ensure system security, you are advised to keep the parameter value of the /proc/sys/net/ipv4/ip_forward file or the value of net.ipv4.ip_forward in the /etc/sysctl.conf file as 0 on the management node. (The default parameter values are 0.)
  • If some disks of a node in the cluster are SSDs, configure the installation environment following the instructions in Configuring the preinstall Script When Some Disks of a Node Are SSDs.
  • If you install the cluster as user omm, perform the preconfiguration as user root in advance. For details, see Configuring the Software Package.
  • If you install the cluster as user omm, obtain the password of user omm in advance.
  • The OS image has been mounted.
  • If multiple RAID levels exist on a node except the OS disk (for example, when the management node and data node are deployed on the same server, RAID 1 for metadata disks and non RAID for data disks exist on a node at the same time), preinstall cannot be used for creating partitions. If this happens, manually mount required partitions. For details, see Appendix > Common Problems > Manually Creating a Partition. Then perform the following operations:

    Delete the node with multiple RAID levels from the g_hosts value in the preinstall.ini file in Manually Creating a Partition (for example, if host0 has multiple RAID levels, delete 192.168.10.10.)

    Delete the node with multiple RAID levels from the g_parted_conf value in the preinstall.ini file in Step 4 (for example, if host0 has multiple RAID levels, delete 192.168.10.10:host0.ini.)

Procedure

  1. Use PuTTY to log in to the active management node as user root (If you install the cluster as user omm, log in to the node as user omm), and run the following command to disable logout upon timeout:

    TMOUT=0

  2. Check whether to encrypt disk partitions and generate an encryption configuration file.

  3. Prepare a key for partition encryption.

    1. On the active management node, run the following command with the account used for cluster installation to switch to the key management directory.

      cd /opt/FusionInsight_SetupTool/preinstall/partition/ini-plugin/keys

    2. Run the following commands to generate two access keys:

      dd if=/dev/random of=fi_disk_key_1 bs=4k count=1

      dd if=/dev/random of=fi_disk_key_2 bs=4k count=1

      The key name cannot be modified. Store primary and secondary access keys on a backup server outside the cluster.

  4. Go to the directory where the installation script tool package is decompressed, for example, /opt/FusionInsight_SetupTool/preinstall. Check whether the preinstall.ini file generated by the FusionInsight Configuration Planning Tool has been uploaded to this directory. If this file is not uploaded or updated, see Generating the Configuration Files to upload the file.

    cd /opt/FusionInsight_SetupTool/preinstall

    cat preinstall.ini

    g_hosts="192.168.10.[10-20]" 
    g_user_name="root" 
    g_port=22 
    g_parted=2 
    g_parted_conf="192.168.10.10:host0.ini;192.168.10.11:host1.ini;192.168.10.12:host2.ini;192.168.10.13:host3.ini; 
    192.168.10.14:host4.ini;192.168.10.15:host5.ini;192.168.10.16:host6.ini;192.168.10.17:host7.ini; 
    192.168.10.18:host8.ini;192.168.10.19:host9.ini;192.168.10.20:host10.ini;" 
    g_add_pkg=1 
    g_pkgs_dir="redhat-6.4:/media/" 
    g_log_file="/tmp/fi-preinstall.log" 
    g_debug=0 
    g_hostname_conf="192.168.10.10:192.168.20.10:host0;192.168.10.11:192.168.20.11:host1;192.168.10.12:192.168.20.12:host2;192.168.10.13:192.168.20.13:host3;192.168.10.14:192.168.20.14:host4;192.168.10.15:192.168.20.15:host5;192.168.10.16:192.168.20.16:host6;192.168.10.17:192.168.20.17:host7;192.168.10.18:192.168.20.18:host8;192.168.10.19:192.168.20.19:host9;192.168.10.20:192.168.20.20:host10;" 
    g_swap_off=1
    g_platform="x86_64"

  5. (Optional) Perform the following operations to enable the disk cache.

    • For sites having the supercapacitor of the RAID controller card configured, enable the disk cache to improve disk performance. In other scenarios, skip this step.
    • In abnormal power-off scenarios, if the disk cache is enabled, data loss may occur. Therefore, exercise caution when enabling this function.
    1. Run the vi preinstall.ini command to open the preinstall configuration file.
    2. Add g_wce_conf=1 (content in bold in the following information) to the configuration file.
      g_hosts="192.168.10.[10–20]" 
      g_user_name="root" 
      g_port=22 
      g_parted=2 
      g_parted_conf="192.168.10.10:host0.ini;192.168.10.11:host1.ini;192.168.10.12:host2.ini;192.168.10.13:host3.ini; 
      192.168.10.14:host4.ini;192.168.10.15:host5.ini;192.168.10.16:host6.ini;192.168.10.17:host7.ini; 
      192.168.10.18:host8.ini;192.168.10.19:host9.ini;192.168.10.20:host10.ini;" 
      g_add_pkg=1 
      g_pkgs_dir="redhat-6.4:/media/" 
      g_log_file="/tmp/fi-preinstall.log" 
      g_debug=0 
      g_hostname_conf="192.168.10.10:192.168.20.10:host0;192.168.10.11:192.168.20.11:host1;192.168.10.12:192.168.20.12:host2;192.168.10.13:192.168.20.13:host3;192.168.10.14:192.168.20.14:host4;192.168.10.15:192.168.20.15:host5;192.168.10.16:192.168.20.16:host6;192.168.10.17:192.168.20.17:host7;192.168.10.18:192.168.20.18:host8;192.168.10.19:192.168.20.19:host9;192.168.10.20:192.168.20.20:host10;" 
      g_swap_off=1
      g_platform="x86_64"
      g_wce_conf=1
    3. Run the :wq! command to save the configuration and exit.

  6. Run the pre-installation configuration command.

    cd /opt/FusionInsight_SetupTool

    ./setuptool.sh preinstall

    Enter the password of user root and wait for the configuration to complete (If you install the cluster as user omm, enter the password of user omm).

    NOTE:
    • By default, after the preinstall is successfully executed, the precheck will be executed automatically.
    • When the -n parameter is used, the precheck will not be executed after the preinstall is executed.
    • When the -c parameter is used, the precheck will always be executed after the preinstall is executed.
    Please enter cluster SSH password:            #Enter the password of user root or omm. 
    **FusionInsight PreInstall is starting... 
     
    ********************************** 
    *****FusionInsight Preinstall***** 
    ********************************** 
    ***** Time:60s 
    ***** Running:0 
    ***** Success:10 
    ***** Failure:0 
    ***** Total:10 
    ***** Schedule:100%
    NOTE:

    If a fault occurs during the configuration of node OS, go to the /tmp/fi-preinstall.log directory and check the preinstall log file to rectify the fault.

    If errors occur when you run the pre-installation configuration command, see the following common problems for troubleshooting:

  7. After the preinstall script is executed, the precheck script will be automatically executed by default.

    ===========FusionInsight PreCheck is starting...=========== 
    [INFO] start checking each hosts. 
    [INFO] localhost: start parsing the configuration file. 
    [INFO] localhost: parse the configuration file success. 
    ...

  8. The following shows the command output.

    ==========Summary Output============ 
    Environment check failed,you can get more information from /opt/FusionInsight_SetupTool/precheck/log/precheck_failed.log
    You can get more information about the preinstall from /tmp/fi-preinstall.log and /tmp/diskmgt/autopart.log

    Run the following command to view the precheck error log in the specified directory, for example,

    vi /opt/FusionInsight_SetupTool/precheck/log/precheck_failed.log

    ...
    [2017-09-07 16:13:31] [WARNING] 192.168.10.10: Nic 'eth2' invalid config, speed is Unknown!. [checkEnvironmentOnEachHost.sh(checkNics):518](154737)
    [2017-09-07 16:13:28] [ERROR] 192.168.10.15: The available space of the '/var/log' partition is '45' (GB). You are advised to allocate a partition with at least '130'(GB) for the log directory. [checkEnvironmentOnEachHost.sh(getPathinfo):464](73474)
    ...
    NOTE:

    Follow instructions in the Errors That Occur During Installation Environment Check and Solutions to the Errors section to process all messages.

    Problems indicated in the ERROR messages must be solved and whether to solve the problems indicated in the WARNING messages depends on the actual situation.

    After solving the problems, perform the following operations:

    1. Run the following command to perform a precheck task again.

      cd /opt/FusionInsight_SetupTool

      ./setuptool.sh precheck precheck/checkNodes.Config

    2. Enter the password of the user who installs the cluster of each node, and wait for the operation to be completed.
    3. View the precheck error log again. Ensure that all problems indicated in the ERROR messages are solved and the problems indicated in the WARNING messages do not have impact on the installation.

Additional Information

  • Partition formatting results of the preinstall script:

    As shown in the following example. (The node has seven drive letters. The OS occupies drive letter sda, and the other partitions each occupy a drive letter. Only drive letter sda is mounted before the preinstall script is executed.)

    • Partitions before running the script
      [root@mgtomsdat-sh-3-01-1 ~]# df -h         \\Only user root is authorized to run this command before Manager is installed. 
      Filesystem            Size  Used Avail Use% Mounted on 
      /dev/sda2             9.7G  1.8G  7.4G  20% / 
      /dev/sda7             371G 15G  338G 5% /opt 
      /dev/sda6              60G 15G 45G  25% /srv/BigData 
      /dev/sda3             9.7G  152M  9.0G 2% /tmp 
      /dev/sda5             9.7G  3.7G  5.5G  41% /var 
      /dev/sda1            58G  1.9G 53G 4% /var/log     
    • Partitions after running the script
      NOTE:

      Run the ll /srv/BigData command to check the permission of the /srv/BigData/LocalBackup directory and ensure that the permission is 700 and owner group is 2000 wheel. Otherwise, run the following commands: (The data storage path can be customized. Default path /srv/BigData is used as an example.)

      chmod 700 /srv/BigData/LocalBackup -R

      chown 2000:wheel /srv/BigData/LocalBackup -R

      [root@mgtomsdat-sh-3-01-1 ~]# df -h        \\Only user root is authorized to run this command before Manager is installed. 
      Filesystem            Size  Used Avail Use% Mounted on 
      /dev/sda2             9.7G  1.8G  7.4G  20% / 
      /dev/sda7             371G 15G  338G 5% /opt 
      /dev/sda6              60G 15G 45G  25% /srv/BigData 
      /dev/sda3             9.7G  152M  9.0G 2% /tmp 
      /dev/sda5             9.7G  3.7G  5.5G  41% /var 
      /dev/sda1              58G  1.9G 53G 4% /var/log 
      /dev/sdb              600G    6G  540G 1% /srv/BigData/zookeeper 
      /dev/sdc              600G    6G  540G 1% /srv/BigData/namenode 
      /dev/sdd              600G    6G  540G 1% /srv/BigData/dbdata_om 
      /dev/sde              600G    6G  540G 1% /srv/BigData/LocalBackup 
      /dev/sdf              600G    6G  540G 1% /srv/BigData/journalnode 
      /dev/sdg              600G    6G  540G 1% /srv/BigData/hadoop/data1     
  • Check items of the precheck script:
    Table 3-2 Major check items

    Check Type

    Check Item

    Hardware

    Checking the CPU of each node

    Checking the memory size of each node

    Checking the number of disks of each node

    Checking the disk capacity and disk mounting methods of all nodes

    • The mounting method of Red Hat and CentOS is UUID.
    • The mounting method of SUSE is by-id.

    Checking the remaining disk partition space

    System configuration

    Checking the host names of all nodes

    Checking whether the directories in the configuration file exist

    Checking whether the /etc/hosts file is correctly configured

    Checking whether the host names conform to the naming rules

    Checking whether the OS contains user omm or the user whose ID is 2000 when the cluster installation is performed by user root

    Checking whether the NTP service has been started

    Checking whether the default or current shared memory meets the GaussDB requirements

    Checking whether the Swap partition is disabled

    Checking the server time zone of each node

    NOTE:

    The server time zone cannot be changed after the cluster is installed.

    Checking the dependency on Omm-j (including GaussDB)

    Checking whether the expect command exists on all nodes

    Checking whether the /etc/ntp.conf file is empty

    Checking whether the /etc/sudoers file is correctly configured

    Checking whether Hadoop programs of other versions have been installed in the OS

    Checking whether user omm has the crontab running permission when the cluster is installed by user omm

    Checking whether the sysctl service can be restarted

    RPM package

    Checking whether python is installed

    Checking whether the python version is correct

    Checking whether SSH is installed

    Checking the RPM package that each component depends on

    NOTE:

    For details, see the OS list file in the /opt/FusionInsight_SetupTool/preinstall/script/function/add_packages/conf directory (for example, redhat-7.4_must-rpms.lst).

    Checking the dependency on lib64.so

    Checking whether the nss-softokn and nss-util RPM packages are installed and whether the version meets the requirements

    OS

    Checking the OS version

    Checking whether the system kernel version meets the requirements

    Checking the NTP version

Download
Updated: 2019-05-17

Document ID: EDOC1100074555

Views: 8210

Downloads: 7

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next