Will the BCC instance exception affect the BLB service?

BLB will actively check the status of the backend BCC instance. BLB will send a new request to other healthy BCC instances if a BCC instance is abnormal, so the entire service can work normally as long as there is a normal BCC instance.

What should I do if the health check status is always abnormal?

1.Make sure that processes/services are listening on the health check port on the cloud host. a) Check whether the BCC instance is normal; b) Check whether the services deployed on the BCC instance are normal, and confirm that there are processes and services listening on the health check port. Note that the health check port of the TCP listener is the same as the backend service port by default.

2.Make sure that the security group policy of the cloud host is properly configured. For details, please see Backend Server Security Group Settings.

3.You can manually request the port of the cloud host to check if it can be accessed normally.

• If you are using TCP health check, you can use the telnet/nmap command to try to establish a TCP connection with the port, eg. Nmap ipaddress -p port;
• If you are using HTTP health check, you can use the curl command to ensure that the HTTP status code returned by the access is 2XX or 3XX, eg. Curl -I ipaddress: port.

4. If the back-end member is an IP address, the IP address should be in the same VPC as the application-oriented BLB instance.