Help Center/ Config/ User Guide/ Resource Compliance/ Built-In Policies/ Elastic Load Balance/ Weight Check for Backend Servers
Updated on 2025-08-25 GMT+08:00
View PDF
Share

Weight Check for Backend Servers

Rule Details

Table 1 Rule details

Parameter

Description

Rule Name

elb-members-weight-check

Identifier

Weight Check for Backend Servers

Description

If the weight of a backend server is 0 and the type of the forwarding rule is not SOURCE_IP, this rule is non-compliant.

Tag

elb

Trigger Type

Configuration change

Filter Type

elb.members

Rule Parameters

Application Scenarios

When you select Weighted round robin or Weighted least connections:

  • If the weights of all backend servers are 0, the load balancer cannot forward traffic, and services will be interrupted.
  • If the weights of some backend servers are 0, other backend servers will handle all traffic, which may cause load imbalance.

When you set the forwarding policy to Source IP Hush or Connection ID:

  • If you change the forwarding policy of a backend server and the backend server weight is 0, service availability will be affected.
  • If you set the weight to 0, the weight will not take effect. You are advised to remove the backend server from its group or set a non-zero weight. For details, see Load Balancing Algorithms.

Solution

If a backend server is no longer required, remove it from the backend server group.

If a backend server is required, configure a proper weight for it to prevent resource waste and misoperations.

Rule Logic

  • If the weight of a backend server is 0, this backend server is non-compliant.
  • If the weight of a backend server is not 0, this backend server is compliant.
Parent topic: Elastic Load Balance