Preparing the Connection Doris Cluster Configuration File

Preparing a Developer Account

For an MRS cluster with Kerberos authentication enabled, you need to prepare a user who has the permission to perform operations on related components for program authentication.

The following Doris permission configuration example is for reference only. You can adjust the permission configuration based on service requirements in actual service scenarios.

1. Log in to FusionInsight Manager.
2. Choose System > Permission > Role > Create Role.
   1. Enter the role name, for example, dorisrole.
   2. In Configure Resource Permission, choose Name of the desired cluster > Doris, select the Doris Admin Privilege, and click OK.

3. Choose User > Create. On the Create user page, create a Human-Machine user, for example, developuser, and bind the user to the 2 New role.
4. Log in to FusionInsight Manager again as the developuser user and change the initial password of the user.

Configuring the Operating Environment Network

Nodes used for program commissioning or running must communicate with nodes in the MRS cluster and the hosts domain name must be configured.

• Scenario 1: Configure the local Windows development environment to communicate with the MRS cluster nodes.
  1. Log in to FusionInsight Manager, click Download Client in the upper right corner of the Homepage, set Select Client Type to Configuration File Only, and click OK. After the client package is generated, download the client as prompted and decompress it.

     For example, if the client configuration file package is FusionInsight_Cluster_1_Services_Client.tar, decompress the package to obtain FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles.tar. Then, decompress the package.

  2. Copy the content in the hosts file in the decompressed directory to the local hosts file.
     

     • During application development, if you need to commission applications in the local Windows system, ensure that the local node can communicate with the hosts listed in the hosts file.
     • For example, the local hosts file is stored in C:\WINDOWS\system32\drivers\etc\hosts on the Windows server.

• Scenario 2: Configure the Linux environment to communicate with the MRS cluster nodes.
  1. Install the MRS cluster client on the node.

     For example, the client installation directory is /opt/hadoopclient.

  2. Obtain the configuration file.
     1. Log in to FusionInsight Manager, click Download Client in the upper right corner of the Homepage, set Select Client Type to Configuration Files Only and click OK. Download the client configuration file to the active OMS node in the cluster.
     2. Log in to the active OMS node as the root user and go to the directory where the client configuration file is stored. The default directory is /tmp/FusionInsight-Client/.

        For example, if the client software package is FusionInsight_Cluster_1_Services_Client.tar, the download path is /tmp/FusionInsight-Client on the active management node.

        cd /tmp/FusionInsight-Client

        tar -xvf FusionInsight_Cluster_1_Services_Client.tar

        tar -xvf FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles.tar

        cd FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles

  3. Check the network connection of the client node.

     During the installation of the client, the system automatically configures the hosts file on the client nodes. You are advised to check whether the /etc/hosts file contains the host names of nodes in the cluster. If not, You need to manually copy the content in the hosts file in the decompressed directory to the hosts file on the node where the client is located to ensure that the local host can communicate with each host in the cluster.