Preparing for Development and Operating Environment

Preparing a Runtime Environment

During application development, you need to prepare the environment for code running and commissioning to verify that the application is running properly.

• If the local Windows development environment can communicate with the cluster service plane network, download the cluster client to the local host; obtain the cluster configuration file required by the commissioning program; configure the network connection, and commission the program in Windows.
  1. Log in to the FusionInsight Manager portal and choose Cluster > Dashboard > More > Download Client. Set Select Client Type to Configuration Files Only. Select the platform type based on the type of the node where the client is to be installed (select x86_64 for the x86 architecture and aarch64 for the Arm architecture) and click OK. After the client files are packaged and generated, download the client to the local PC as prompted and decompress it.

     For example, if the client file package is FusionInsight_Cluster_1_Services_Client.tar, decompress it to obtain FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles.tar file. Then, decompress FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles.tar file to the D:\FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles directory on the local PC. The directory name cannot contain spaces.

  2. Go to the client decompression path FusionInsight_Cluster_1_Services_ClientConfig_ConfigFiles\Spark2x\config and manually import the configuration file to the configuration file directory (usually the resources folder) of the Hive sample project.

     The keytab file obtained during the Preparing the Developer Account is also stored in this directory. Table 2 describes the main configuration files.

     Table 2 Configuration files

     File	Function
     carbon.properties	CarbonData configuration file
     core-site.xml	Configures HDFS parameters.
     hdfs-site.xml	Configures HDFS parameters.
     hbase-site.xml	Configures HBase parameters.
     hive-site.xml	Configures Hive parameters.
     jaas-zk.conf	Java authentication configuration file
     log4j-executor.properties	executor log configuration file
     mapred-site.xml	Hadoop mapreduce configuration file
     ranger-spark-audit.xml	Ranger audit log configuration file
     ranger-spark-security.xml	Ranger permission management configuration file
     yarn-site.xml	Configures Yarn parameters.
     spark-defaults.conf	Configures Spark2x parameters.
     spark-env.sh	Spark2x environment variable configuration file
     user.keytab	Provides HDFS user information for Kerberos security authentication.
     krb5.conf	Provides Kerberos server configuration information.

  3. During application development, if you need to commission the application in the local Windows system, copy the content in the hosts file in the decompression directory to the hosts file of the node where the client is located. Ensure that the local host can communicate correctly with the hosts listed in the hosts file in the decompression directory.
     

     • If the host where the client is installed is not a node in the cluster, configure network connections for the client to prevent errors when you run commands on the client.
     • The local hosts file in a Windows environment is stored in, for example, C:\WINDOWS\system32\drivers\etc\hosts.

• If you use the Linux environment for commissioning, you need to prepare the Linux node where the cluster client is to be installed and obtain related configuration files.
  1. Install the client on the node. For example, install the client in the directory /opt/client.

     Ensure that the difference between the client time and the cluster time is less than 5 minutes.

     For details about how to use the client on a Master or Core node in the cluster, see Using an MRS Client on Nodes Inside a Cluster. For details about how to install the client outside the MRS cluster, see Using an MRS Client on Nodes Outside a Cluster.

  2. Log in to the FusionInsight Manager portal. Download the cluster client software package to the active management node and decompress it. Then, log in to the active management node as user root. Go to the decompression path of the cluster client and copy all configuration files in the FusionInsight_Cluster_1_Services_ClientConfig/Spark2x/config directory to the conf directory where the compiled JAR package is stored for subsequent commissioning, for example, /opt/client/conf.

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

     cd /tmp/FusionInsight-Client

     tar -xvf FusionInsight_Cluster_1_Services_Client.tar

     tar -xvf FusionInsight_Cluster_1_Services_ClientConfig.tar

     cd FusionInsight_Cluster_1_Services_ClientConfig

     scp Spark2x/config/* root@IP address of the client node:/opt/client/conf

     The keytab file obtained during the Preparing the Developer Account is also stored in this directory. Table 3 describes the main configuration files.

     Table 3 Configuration files

     File	Function
     carbon.properties	CarbonData configuration file
     core-site.xml	Configures HDFS parameters.
     hdfs-site.xml	Configures HDFS parameters.
     hbase-site.xml	Configures HBase parameters.
     hive-site.xml	Configures Hive parameters.
     jaas-zk.conf	Java authentication configuration file
     log4j-executor.properties	executor log configuration file
     mapred-site.xml	Hadoop mapreduce configuration file
     ranger-spark-audit.xml	Ranger audit log configuration file
     ranger-spark-security.xml	Ranger permission management configuration file
     yarn-site.xml	Configures Yarn parameters.
     spark-defaults.conf	Configures Spark2x parameters.
     spark-env.sh	Spark2x environment variable configuration file
     user.keytab	Provides HDFS user information for Kerberos security authentication.
     krb5.conf	Provides Kerberos server configuration information.

  3. Check the network connection of the client node.

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