Deployment
This topic provides answers to some frequently asked questions about deployment.
How do I bind a fixed IP address with the priority_networks parameter in the fe.conf file?​
Problem description​
For example, if you have two IP addresses: 192.168.108.23 and 192.168.108.43. You might provide IP addresses as follows:
- If you specify the addresses as 192.168.108.23/24, StarRocks will recognize them as 192.168.108.43.
- If you specify the addresses as 192.168.108.23/32, StarRocks will recognize them as 127.0.0.1.
Solution​
There are the following two ways to solve this problem:
- Do not add "32" at the end of an IP address or change "32" to "28".
- You can also upgrade to StarRocks 2.1 or later.
Why does the error "StarRocks BE http service did not start correctly, exiting" occur when I start a backend (BE) after installation?​
When installing a BE, the system reports a startup error: StarRocks Be http service did not start correctly, exiting.
This error occurs because the web services port of the BE is occupied. Try to modify the ports in the be.conf file and restart the BE.
What do I do when the error occurs: ERROR 1064 (HY000): Could not initialize class com.starrocks.rpc.BackendServiceProxy?​
This error occurs when you run programs in Java Runtime Environment (JRE). To solve this problem, replace JRE with Java Development Kit (JDK). We recommend that you use Oracle's JDK 17 or later.
Can FE and BE configuration items be modified and then take effect without restarting the cluster?​
Yes. Perform the following steps to complete the modifications for an FE and a BE configuration item:
-
FE: You can complete the modification for an FE in one of the following ways:
- SQL
ADMIN SET FRONTEND CONFIG ("key" = "value");Example:
ADMIN SET FRONTEND CONFIG ("enable_statistic_collect" = "false");- Shell
curl --location-trusted -u username:password \
http://<ip>:<fe_http_port/api/_set_config?key=value>Example:
curl --location-trusted -u <username>:<password> \
http://192.168.110.101:8030/api/_set_config?enable_statistic_collect=true -
BE: You can complete the modification for a BE in the following way:
curl -XPOST -u username:password \
http://<ip>:<be_http_port>/api/update_config?key=value
Note: Make sure that the user has permission to log in remotely. If not, you can grant the permission to the user in the following way:
CREATE USER 'test'@'%' IDENTIFIED BY '123456';
GRANT SELECT ON . TO 'test'@'%';
Why does the error "Fe type:unknown ,is ready :false." occur when I start an FE during the cluster restart?​
Check if the leader FE is running. If not, restart the FE nodes in your cluster one by one.
Why does the error "failed to get service info err." occur when I deploy the cluster?​
Check if OpenSSH Daemon (sshd) is enabled. If not, run the /etc/init.d/sshd`` status command to enable it.