Project: StarRocks (App Definition and Development / Database)
File: Deploy_faq.md

displayed_sidebar: "English" This topic provides answers to some frequently asked questions about deployment. 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. 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. 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 1.8 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: SQL ```plaintext ADMIN SET FRONTEND CONFIG ("key" = "value"); ``` Example: ```plaintext ADMIN SET FRONTEND CONFIG ("enablestatisticcollect" = "false"); ``` Shell ```plaintext curl --location-trusted -u username:password \ http://<ip>:<fehttpport/api/setconfig?key=value> ``` Example: ```plaintext curl --location-trusted -u <username>:<password> \ http://192.168.110.101:8030/api/setconfig?enablestatisticcollect=true ``` BE: You can complete the modification for a BE in the following way: ```plaintext curl -XPOST -u username:password \ http://<ip>:<behttpport>/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: ```plaintext CREATE USER 'test'@'%' IDENTIFIED BY '123456'; GRANT SELECT ON . TO 'test'@'%'; ``` This error may occur during data loading into Primary Key tables. During data loading, the destination BE does not have enough disk space for the loaded data and the BE crashes. New disks are then added to extend the disk space. However, Primary Key tables do not support disk space re-balancing and the data cannot be offloaded to other

Patches to this bug (Primary Key tables do not support BE disk space re-balancing) is still under active development. Currently, you can fix it in either of the following two ways: Manually distribute data among disks. For example, copy the directory from the disk with a high space usage to a disk with a larger space. If the data on these disks is not important, we recommend you delete the disks and modify the disk path. If this error persists, use to clear data in the table to free up some space. 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. 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. <!-- This error occurs when the disk space specified in the deployment directory is insufficient. During the cluster upgrade, the StarRocks Manager distributes the binary file of the new version to each node. If the disk space specified in the deployment directory is insufficient, the file cannot be distributed to each node. To solve this problem, add data disks. --> 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. Configure the `storagerootpath` parameter in the `be.conf` file and separate values of this parameter with `;`. For example: `storagerootpath=/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. 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.