Table of Contents generated with DocToc
Minimum Configuration
Recommended Configuration
mkdir hengshi-sense-[version] && unzip -qod hengshi-sense-[version]/ hengshi-sense-[version].zip
Using cloud service PostgreSQL to replace Hengshi metadb
Standalone installation process
Post-installation configuration
Standalone/Cluster service operations
$ /opt/hengshi/bin/hengshi-sense-bin init-os systemd
$ sudo systemctl enable hengshi
$ sudo systemctl disable hengshi
sudo systemctl stop hengshi
sudo systemctl start hengshi
sudo systemctl status hengshi
High availability engine configuration
There are two configuration files: (they do not exist by default)
Note:
This configuration is only necessary when installing the acceleration engine.
Without the configuration file the system will run with default parameters
All configuration items need to be written into the conf/hengshi-sense-env.sh file
Parameter | Purpose |
---|---|
JAVA_HOME | Set the runtime Java environment directory (needs to be set to a Java 1.8 environment) |
HS_HENGSHI_PORT | Change Hengshi WEB service port, default 8080 (BI prohibits root startup, below 1024 port please configure proxy forwarding, such as Nginx, etc.) |
HS_HENGSHI_DATA | The root directory where hengshi stores all data, defaults to the installation directory, you can configure this variable when there is a large partition specifically for data storage |
HS_PG_HOST | Host of the internal database program, if not using the built-in one, such as RDS, can be set through this variable |
HS_PG_PORT | The listening port of the internal database program (54320), if it conflicts with existing service ports it can be changed through this variable |
HS_PG_DB | Database name of the internal database program |
HS_PG_USR | Username for the internal database program |
HS_PG_PWD | Password for the internal database program |
HS_ENGINE_HOME | Path for engine data files |
HS_ENGINE_HOST | Engine host, after configuration the master module of the engine will be deployed on the corresponding machine, default is localhost |
HS_ENGINE_SEGMENTS | Engine worker nodes, array, default is (localhost); example for multiple nodes: (Node-A Node-B Node-C) |
HS_ENGINE_PORT | Engine port |
The product requires that uploaded files do not exceed 50MB. If you configure a reverse proxy, you need to configure the file upload size; taking Nginx as an example:
# For configuration file such as /etc/nginx/nginx.conf, configure in the corresponding server
client_max_body_size 100m;
# For configuration file such as /etc/nginx/nginx.conf, configure in the corresponding server
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;
The product cannot be started by root, cannot bind ports below 1024. If you need to listen on ports 80, 443, it is recommended to use Nginx for reverse proxying.
# hengshi proxy
upstream hengshi_proxy {
server $IP:$PORT;
}
server {
server_name $SERVNAME;
access_log /var/log/nginx/access.log main;
listen 80;
location / {
proxy_pass http://hengshi_proxy;
}
}
server {
server_name $SERVNAME
listen 443 ssl http2 ;
access_log /var/log/nginx/access.log main;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
ssl_ciphers '...';
ssl_prefer_server_ciphers on;
ssl_session_timeout 5m;
ssl_session_cache shared:SSL:50m;
ssl_session_tickets off;
ssl_certificate $PATH_TO_CER
ssl_certificate_key $PATH_TO_CER_KEY
add_header Strict-Transport-Security "max-age=31536000" always;
location / {
proxy_pass http://hengshi_proxy;
}
}
where variables need to be replaced with actual values
If the version of the database to connect to is listed in the "Special Data Source Version JDBC Driver Table", you need to download the respective version of the driver and perform the following operations:
Special Data Source Version JDBC Driver Table:
Server Version | Download Address |
---|---|
hive-1.1 | https://download.hengshi.io/3rd/hive-1.1-jdbc-minimal.zip |
Note: After placing a JDBC driver in the plugins directory, you can only connect to the corresponding version of the service. Connectivity to other versions of the service cannot be guaranteed. For example, if you download the hive-1.1 driver and put it in the plugins directory, only connectivity to hive-1.1 can be guaranteed, and connectivity to other hive versions is no longer guaranteed.