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


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


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 Cluster

Installing a Cluster


Use a template to perform automatic cluster installation. For details about how to view the installation logs, see Viewing Installation Logs.

Impact on the System

During the cluster installation, the OS firewall of each node is automatically disabled by the installation script to ensure communication in the cluster. If the firewall needs to be enabled, see the FusionInsight HD 6.5.0 Communication Matrix to enable the ports manually.


For security, you are advised to disable the remote access permission of user root on each node after the cluster is installed.


Installing Manager on Two Management Nodes is complete.

The default SSH port No. (22) is used for each node in the cluster. Otherwise, the task in this section will fail.


Configuring the Browser

  1. On Internet Explorer, click, choose Internet Options. In the displayed Internet Options dialog box, click the Advanced tab page.


    On Google Chrome, click, choose Settings > Show advanced settings... > Network > Change proxy settings.... In the Internet Properties dialog box that is displayed, click the Advanced tab.

  2. In the Settings area, deselect Use SSL 2.0 and Use SSL 3.0, and select Use TLS 1.1, and Use TLS 1.2, as shown in Figure 3-2.

    Figure 3-2 Internet Options

    If your browser is Internet Explorer 11, set the compatibility mode. Click and choose Compatibility View settings. In the displayed Compatibility View Settings dialog box, deselect Display intranet sites in Compatibility View and click Close.

Logging in to FusionInsight Manager.

  1. Log in to FusionInsight Manager.

    Enter the network address of FusionInsight Manager in the address box of the browser.

    The address format is http://WebService floating IP address of FusionInsight Manager system:8080/web.

    For example, enter

    Enter your username (admin) and password (Admin@123).

    • Clear the browser cache at first login.
    • If the certificate is not installed yet, a certificate error is displayed. Click Continue to this website.
    • The password needs to be changed at the first login.

    Default user password policies:

    • The password contains at least 8 characters.
    • The password must contain at least four types of the following: lowercase letters, uppercase letters, numerals, and special characters which can only be ~`!?,.:;-_'"(){}[]/<>@#$%^&*+|\=.
    • The password cannot be the same as the username or reverse username.
    • The password cannot be the same as the previous password.

Installing the Cluster

  1. Click Create Cluster, select Template Installation and select the template (install_cluster\installTemplet.xml, for details about template installation methods, see Generating the Configuration Files). Click OK.

    • Internet Explorer 9 supports only manual cluster installation and does not support template-based installation. You are advised to use Internet Explorer 11 or Chrome. For details, see Preparing Tools and Software.
    • If the installation template cannot be loaded, manually install a cluster. For details, see Installing a Cluster.
    • Enter the password of user root (or user omm) in Discover Hosts > Password and click Start Discovery to discover the node.
    • After the template is imported, the OK page is displayed. If the configuration planning data on the displayed page is incorrect, click Previous to check or modify the parameter values.

  2. Click Previous to return to Service Configuration tab, select the related services in Service. Reset the parameters of related services based on Table 3-3.

    Table 3-3 Setting parameters






    If the number of Solr service nodes exceeds 50, it is recommended that the GC_OPTS parameter of the Zookeeper quorumpeer instance be set to the following values: -Xmx be set to 8G and -XX:MaxDirectMemorySize be set to 2G.



    If the number of nodes with the DataNode role is less than 10, change the value to the actual number of DataNode nodes.


    • ftp-enabled
    • ftp-server-ip
    • Options:
      • true (The ftp protocol is enabled.)
      • false (The ftp protocol is disabled. This is the default value.)

    To ensure data security, it is recommended that the ftps protocol that provides higher security be used during data transmission.

    • Indicates the IP address that provides the FTP service on the node where the FTP-Server service is installed. The default value is the service plane IP address of the node. If the default value is to be changed, the user needs to add an IP address to the network port of the node. The user also needs to delete the added IP address when uninstalling the FTP-Server service.



    The umask used when creating files and directories. Can be in octal or in symbolic. For example,

    • 022 (octal for u=rwx, g=r-x, o=r-x in symbolic)
    • u=rwx, g=rwx, o= (symbolic for 007 in octal)

    The default value is 077.



    Installation mode of the Redis component. Value:

    • true (security mode)
    • false (normal mode)

    The security mode deteriorates the performance. You are advised to install the normal mode if there is no special requirement. (If Redis is accessed in normal mode, authentication or authorization is not required. Do not use Redis to store important data; otherwise, security risks may exist.)


    • offsets.topic.replication.factor
    • transaction.state.log.replication.factor

    The replication factor for the Kafka inner topic.


    When the number of Broker instances is 2, change the number of internal Topic copies to 2.


    When the physical memory of the node where a service role locates is smaller than 24 GB, set GC_Profile of the service role to low.

  3. Click Next to go to the OK tab to confirm the configuration information. Click Submit. In the displayed dialog box, determine whether to select Start the Cluster after installation..

    • If yes, click OK to start the installation and start the cluster. After the cluster is installed and started, click Finish.
    • If no, go to Step 7.

  4. Click OK to install the cluster. After the cluster is installed, determine whether to start the cluster in the displayed dialog box.

    • If yes, click Yes to start the cluster. After the cluster is started, click Finish.
    • If no, click No to go to the FusionInsight Manager page. You can start the services manually.

    If errors occur when you install the cluster, see Installing the Cluster.

  5. Expand the capacity of heterogeneous servers if necessary, for example, expand the capacity of an ARM server on an x86 cluster. For details, see FusionInsight HD Capacity Expansion Guide.
  6. To manually add new service instances after installing a cluster in the multi-service scenario, follow the instructions in section Installing a Service by choosing Appendix > Installation Process (Perform Manual Installation).
  7. Determine whether to install the cluster as user omm.

    • If yes, go to Step 11.
    • If no, no further action is required.

  8. Use PuTTY to log in to the active management node as user root.
  9. Run the sh /opt/preset/ command on all nodes.


    The postset script is used to reclaim the cluster uninstallation permission of user omm. You can obtain the postset script from the FusionInsight_SetupTool/preset directory where the script installation tool package is decompressed.

    You can use the script tool in the software package to run a command or access a file on multiple nodes in a cluster. For details, see How to Run Commands or Access Files on Multiple Nodes in a Cluster.

Updated: 2019-05-17

Document ID: EDOC1100074555

Views: 5672

Downloads: 6

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