Classic CLB routes requests to real server instances that are running normally. This document describes how to add or delete real servers as needed or when you use Classic CLB for the first time.
You have created a Classic CLB instance and configured a listener. For more information, please see Getting Started with Classic CLB.
Note:
- If a Classic CLB instance is associated with an auto scaling group, CVM instances in the group will be automatically added to the real servers of the Classic CLB instance. When a CVM instance is removed from the auto scaling group, it will be automatically deleted from the real servers of the Classic CLB instance.
- If you need to use API to add real servers, please see the RegisterTargetsWithClassicalLB API.
Note:
You need to specify the real server port for Classic CLB during listener creation.
Note:
- The pop-up window only displays available CVM instances in the same region and same network environment that are not isolated and have not expired with peak bandwidth greater than 0.
- When multiple real servers are bound, CLB will forward traffic according to the hash algorithm to balance the load.
- The greater the weight of a server, the more the requests forwarded to it. The default value is 10, and the configurable value range is 0–100. If the weight is set to 0, the server will not accept new requests. If session persistence is enabled, it may cause uneven request distribution among real servers. For more information, please see Algorithms and Weight Configuration.
Note:
Currently, real server weight cannot be modified through APIs for Classic CLB.
Note:
The greater the weight of a server, the more the requests forwarded to it. The default value is 10, and the configurable value range is 0–100. If the weight is set to 0, the server will not accept new requests. If session persistence is enabled, it may cause uneven request distribution among real servers. For more information, please see Algorithms and Weight Configuration.
Note:
After the batch modification, the servers will have the same weight.
Note:
- Unbinding a real server will unbind the Classic CLB instance from the CVM instance, and Classic CLB will stop forwarding requests to it immediately.
- Unbinding a real server will not affect the lifecycle of your CVM instance, which can be added to the real server cluster again when necessary.
- If you need to use API to unbind real servers, please see the DeregisterTargetsFromClassicalLB API.
Was this page helpful?