Deploying openLooKeng Automatically

In addition to the manual deployment of openLooKeng Sever, you can follow below guide to complete the deployment faster and easier. The script is friendly to most of Linux OS. However, to Ubuntu, you need to manually install the following dependencies:

sshpass1.06 or above

Deploying openLooKeng on a Single Node

Executing the below command can help you download the necessary packages and deploy openLooKeng server in one-click:

bash <(wget -qO-


wget -O -|bash

Normally, you don't need to do anything, except waiting for the installation to complete. It will automatically start the service.

Execute below command to stop openLooKeng service.:


Execute below command to start openLooKeng Command Line client:


Deploying openLooKeng to Cluster online

Execute below command to install openLooKeng cluster:

bash <(wget -qO- -m


bash <(wget -qO- --multi-node

First, this command will download scripts and packages required by openLooKeng service. After the download is completed, it will check whether the dependent packages expect and sshpass are installed. If not, those dependencies will be installed automatically.

Besides, jdk version is required to be greater than 1.8.0_151. If not, jdk1.8.0_201 will be installed in the cluster. It is recommended to manually install these dependencies before installing openLooKeng service.

Secondly, the script will download openLooKeng-server tarball and copy that tarball to all the nodes in the cluster. Then install the openLooKeng-server by using this tarball.

Lastly, the script will setup openLooKeng server with the standard configurations, includes configurations for JVM, Node and for built-in catalogs like tpch, tpcds, memory connector.

By design, the script will check if there are existing configuration under directory: /home/openlkadmin/.openlkadmin/cluster_node_info

If this file is missing, the install script will ask user to input the nodes information.

Optionally, you can add user openlkadmin and create a file /home/openlkadmin/.openlkconf/cluster_node_info.

In the cluster_node_info, you should list appropriate values for your cluster.

Please refer to below template, and replace the variables denoted with brackets <> with actual values.


The general configurations for openLooKeng's coordinator, workers are taken from the configuration file /home/openlkadmin/.openlkadmin/cluster_config_info and configurations for connectors are taken from the directory /home/openlkadmin/.openlkadmin/catalog respectively. If these directories or any required configuration files are absent during the deploy script running, default configuration files will be generated automatically and deployed to all nodes.

Which means, alternatively, you can add those configuration files before running this deploy script, if you want to customize the deployment.

If all the above processes succeed, the deploy script will automatically start the openLooKeng Service for you. Execute below command to stop openLooKeng service.:


Execute below command to start openLooKeng Command Line client.:



If you are going to deploy openLooKeng on a big cluster with lots of nodes, instead of inputting the nodes’ IP address one by one. It is better to prepare a file containing all nodes’ IP address then pass this file as parameter to the installation script. Here is the command:

bash <(wget -qO- -f <cluster_node_info_path>


bash <(wget -qO- --file <cluster_node_info_path>

For more help, execute below command to deploy single node cluster:

bash <(wget -qO- -h


bash <(wget -qO- --help

Upgrade openLooKeng Service

Execute below command to Upgrade openLooKeng Service:

bash <(wget -qO- -u <version>

This command will upgrade the current openLooKeng Service to target version, preserving all the existing configurations on current cluster. Execute below command to list all available versions:

bash <(wget -qO- -l


bash <(wget -qO- --list

Deploying Configuration to openLooKeng Cluster

Modify configuration file (/home/openlkadmin/.openlkadmin/cluster_config_info) and then execute below command to deploy the configurations to openLooKeng cluster:

bash /opt/openlookeng/bin/

Note, if you want to add more configurations or customize the configurations, you can add properties to the templates into file located at /home/openlkadmin/.openlkadmin/.etc_template/coordinator or /home/openlkadmin/.openlkadmin/.etc_template/worker.

The property format must be key=<value>, where value is wrapped with '<' and '>', which means it is a dynamic value. For example:


Next, you need to add the actual value into configuration file /home/openlkadmin/.openlkadmin/cluster_config_info. For example:


Uninstall openLooKeng Service

It is very easy and straight forward to uninstall openLooKeng Service, simply run below command:

bash /opt/openlookeng/bin/

This will uninstall openLooKeng Service by removing directory /opt/openlookeng and all files inside it. However, the openlkadmin user and all the configuration files under/home/openlkadmin/ will not be removed. If you want to delete user and configuration files, you need to run the below command:

bash /opt/openlookeng/bin/ --all

Deploying openLooKeng to Cluster offline

If you can’t access the download URL from the machine where you want to install openLooKeng, you can download all required files beforehand and install offline.

  1. Download and extract its content to /opt.

  2. Create folder /opt/openlookeng/resource and save openLooKeng binary files under it:<version>/hetu-server-<version>.tar.gz and<version>/hetu-cli-<version>-executable.jar, where <version> refers to the version being installed, e.g. 1.0.0.

  3. Also save third party dependencies under /opt/openlookeng/resource. That is, download all files from either or, depending on the machine’s architecture. This should include 1 OpenJDK file and 2 sshpass files.

  4. If you plan to perform multi-node installation, and some nodes in the cluster have a different architecture type from the current machine, then also download the OpenJDK file for the other architecture and save it under /opt/openlookeng/resource/<arch>, where <arch> is either x86 or aarch64, corresponding to the other architecture.

After all resources are available, execute below command to deploy single node cluster:

bash /opt/openlookeng/bin/

Execute below command to deploy multi-node cluster:

bash /opt/openlookeng/bin/ -m


bash /opt/openlookeng/bin/ --multi-node

execute the below command to get help on all available options:

bash /opt/openlookeng/bin/ --help

Adding Node to Cluster

If you want to add node to make the cluster bigger, execute the below command:

bash /opt/openlookeng/bin/ -n <ip_address_1,……ip_address_N>


bash /opt/openlookeng/bin/ --node <ip_address_1,……ip_address_N>


bash /opt/openlookeng/bin/ -f <add_nodes_file_path>


bash /opt/openlookeng/bin/ --file <add_nodes_file_path>

If there are multiple nodes, separated by commas (,). add_ nodes_ File example: ip_address_1,ip_address_2……,ip_address_N.

Removing Node to Cluster

If you want to remove node to make the cluster smaller, execute the below command:

bash /opt/openlookeng/bin/ -n <ip_address_1,……ip_address_N>


bash /opt/openlookeng/bin/ --node <ip_address_1,……ip_address_N>


bash /opt/openlookeng/bin/ -f <remove_nodes_file_path>


bash /opt/openlookeng/bin/ --file <remove_nodes_file_path>

If there are multiple nodes, separate them with commas (,). add_ nodes_ File example: ip_address_1,ip_address_2……,ip_address_N.

See Also

Deploying openLooKeng Manually