When Will the Changes to Server Weights Be Applied?

The changes are applied within 5 seconds.

• If the server is in a TCP, TLS, or UDP backend server group, requests are routed to this server over new connections based on the new weight. However, requests are routed to this server over existing connections still based on the previous weight.
• If the server is in an HTTP, HTTPS, or QUIC backend server group, new requests are routed to this server based on the new weight, while existing requests are routed to this server based on the previous weight.

For TCP, UDP, and QUIC backend server groups, if the weight of a backend server is changed to 0, the load balancer handles traffic differently depending on whether Deregistration Delay is enabled:

• If Deregistration Delay is disabled, no new traffic will be sent to the backend server, and existing persistent connections will be disconnected immediately.
• If Deregistration Delay is enabled, no new traffic will be sent to the backend server, but in-flight requests will still be routed to the server over the existing persistent connection until the deregistration delay timeout expires. After deregistration delay timeout expires, the existing persistent connection will be disconnected.
• If you want new traffic to be blocked and existing persistent connections to be kept active after the weight of a backend server is changed to 0, submit a service ticket. However, if no requests are routed over an existing persistent connection when the idle timeout expires, the load balancer closes this connection.

For HTTP, HTTPS, and TLS backend server groups, after the weight of a backend server is changed to 0, no new traffic goes to this server, and existing persistent connections are disconnected after the response timeout expires.