How Do I Handle the Startup Failure Due to Incorrect IP Address Matching for the BE Instance?

Symptom

The BE instance failed to be started and the following error message was displayed:

backend ip saved in master does not equal to backend local ipx.x.x.x vs. x.x.x.x

Cause Analysis

Search for local host ip in the be.INFO file and check whether the IP address is the IP address of the BE in the show backends command output. If it is not, there are multiple network adapters. In this case, set priority_networks to specify the network IP address range.

Procedure

1. Log in to FusionInsight Manager and choose Cluster > Services > Doris, and click Configurations.
2. Search for the priority_network parameter and set it correctly. To view the IP address of the NIC bound to the BE node, connect the MySQL client to Doris and run show backends;.

   The priority_network parameter is used to help the system select the correct IP address of the network adapter as the IP address of the FE or BE. You are advised to set this parameter explicitly in any case to prevent incorrect IP address selection after network adapters are added. The value of priority_network is in CIDR format and is used to ensure that all nodes can use the same configuration value. The parameter value consists of two parts. The first part is the IP address in dotted decimal notation, and the second part is the prefix length.

   For example, 10.168.1.0/8 matches all 10.xx.xx.xx IP addresses, and 10.168.1.0/16 matches all 10.168.xx.xx IP addresses. If there are two nodes: 10.168.10.1 and 10.168.10.2, 10.168.10.0/24 can be the value of priority_network.