docs/en/faq/Deploy_faq.md
This topic provides answers to some frequently asked questions about deployment.
priority_networks parameter in the fe.conf file?For example, if you have two IP addresses: 192.168.108.23 and 192.168.108.43. You might provide IP addresses as follows:
There are the following two ways to solve this problem:
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.
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.
<!-- ## Why does the error "Failed to Distribute files to node" occur when I deploy StarRocks of Enterprise Edition and configure nodes? This error occurs when Setuptools versions installed on multiple frontends (FEs) are inconsistent. To solve this problem, you can execute the following command as a root user. ```plaintext yum remove python-setuptools rm /usr/lib/python2.7/site-packages/setuptool* -rf wget https://bootstrap.pypa.io/ez_setup.py -O - | python ``` -->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:
ADMIN SET FRONTEND CONFIG ("key" = "value");
Example:
ADMIN SET FRONTEND CONFIG ("enable_statistic_collect" = "false");
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'@'%';
Check if the leader FE is running. If not, restart the FE nodes in your cluster one by one.
Check if OpenSSH Daemon (sshd) is enabled. If not, run the /etc/init.d/sshd`` status command to enable it.
cache. ``host= port=0 code=THRIFT_RPC_ERROR" occur when I start a BE?Run the netstat -anp |grep port command to check whether the ports in the be.conf file are occupied. If so, replace the occupied port with a free port and then restart the BE.
By default, StarRocks Manager obtains the path configuration of the newly deployed FE within 30 seconds. This error occurs when the FE starts slowly or does not respond within 30 seconds due to other reasons. Check the log of Manager Web via the path:
/starrocks-manager-xxx/center/log/webcenter/log/web/``drms.INFO(you can customize the path). Then find that whether the message "Failed to update FE configurations" display in the log. If so, restart the corresponding FE to obtain the new path configuration.
This error occurs when the time difference between two machines is more than 5s. To solve this problem, align the time of these two machines.
storage_root_path parameter if there are multiple disks in a BE for data storage?Configure the storage_root_path parameter in the be.conf file and separate values of this parameter with ;. For example: storage_root_path=/the/path/to/storage1;/the/path/to/storage2;/the/path/to/storage3;
If you do not add the --helper option for this FE when starting your cluster for the first time, the metadata between two machines is inconsistent, thus this error occurs. To solve this problem, you need to clear all metadata under the meta directory and then add an FE with the --helper option.
false when an FE is running and prints log transfer: follower?This issue occurs when more than half of memory of Java Virtual Machine (JVM) is used and no checkpoint is marked. In general, a checkpoint will be marked after the system accumulates 50,000 pieces of log. We recommend that you modify the JVM's parameters of each FE and restarting these FEs when they are not heavily loaded.
$JAVA_HOME points to the correct JDK path.MySQL 5.7 or later is recommended to connect to StarRocks.
It is recommended to scale out a BE node first. After the cluster finishes balancing, you can then scale in the original BE node.
The clocks between FE nodes are not synchronized. The time difference between FE nodes must be less than 5 seconds.
A recommended deployment is 3 FE nodes and 5 BE nodes.
It is not recommended to use the root user because it has excessive privileges. Create a dedicated user for installing StarRocks.
Yes. It is simply a client tool and does not need to run on the same machine as StarRocks. Make sure the MySQL client can access the cluster.
There is no strict limit for the tablet number. However, for the tablet size, it is recommended to keep each tablet around 1 GB. Proper partitioning and bucketing strategies will help improve query performance. Tablet size planning is important.
lib/starrocks_be, I get a permission denied error. What should I do?There is an issue with the JDK installation. Please reinstall and properly configure your JDK environment.
StarRocks can run on AMD. Mixing Intel and AMD servers is not recommended because hardware heterogeneity may cause issues. It is suggested to fully test StarRocks on AMD before migrating.