Stickiness Duration (min)
|
Specifies the minutes that sticky sessions are maintained.
-- Layer 4:
- Default: 20 minutes
- Maximum: 1 hour
- Range: 1 minute to 60 minutes
- - Layer 7:
- Default: 20 minutes
- Maximum: 24 hours
- Range: 1 minute to 1,440 minutes
+- Layer 4:
- Default: 20 minutes
- Maximum: 60 minutes
- Range: 1 minute to 60 minutes
+ - Layer 7:
- Default: 20 minutes
- Maximum: 1,440 minutes
- Range: 1 minute to 1,440 minutes
|
20
@@ -185,9 +188,9 @@
Click OK.
-Modifying a Backend Server Group- Log in to the management console.
- In the upper left corner of the page, click
 and select the desired region and project. - Hover on
 in the upper left corner to display Service List and choose Network > Elastic Load Balancing. - Locate the load balancer and click its name.
- Click Backend Server Groups, locate the backend server group, and click
 on the right of its name. - Modify the parameters as needed and click OK.
+ Modifying a Backend Server Group- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Locate the load balancer and click its name.
- Click Backend Server Groups, locate the backend server group, and click on the right of its name.
- Modify the parameters as needed and click OK.
-
diff --git a/docs/elb/umn/elb_ug_hd_0004.html b/docs/elb/umn/elb_ug_hd_0004.html
index 1565457a..f21f5309 100644
--- a/docs/elb/umn/elb_ug_hd_0004.html
+++ b/docs/elb/umn/elb_ug_hd_0004.html
@@ -3,7 +3,7 @@
Enabling Removal Protection for Backend Servers
ScenariosDedicated load balancers allow you to enable removal protection for associated backend servers to prevent them from being removed by accident.
- Procedure- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on
 in the upper left corner to display Service List and choose Network > Elastic Load Balancing. - On the Load Balancers page, locate the load balancer and click its name.
- Click Backend Server Groups, locate the backend server group, and click its name.
- In the Basic Information area on the right, enable Removal Protection.
+
diff --git a/docs/elb/umn/elb_ug_hd_0005.html b/docs/elb/umn/elb_ug_hd_0005.html
index c8164e2d..2f9a1a9c 100644
--- a/docs/elb/umn/elb_ug_hd_0005.html
+++ b/docs/elb/umn/elb_ug_hd_0005.html
@@ -1,15 +1,18 @@
Configuring Hybrid Load Balancing
- ScenariosYou can add servers in the VPC where the load balancer is created, in a different VPC, or in an on-premise data center, by using private IP addresses of the servers. In this way, incoming traffic can be flexibly distributed to cloud servers and on-premises servers for hybrid load balancing.
+ ScenariosYou can add servers in the VPC where the load balancer is created, in a different VPC, or in an on-premises data center, by using private IP addresses of the servers. In this way, incoming traffic can be flexibly distributed to cloud servers and on-premises servers for hybrid load balancing.
- To add servers in the same VPC as the load balancer, see Adding or Removing Backend Servers (Dedicated Load Balancers).
- To add backend servers in a different VPC from where the load balancer is running, you need to establish a VPC peering connection between the two VPCs. For details about how to set up a VPC peering connection, see the Virtual Private Cloud User Guide.
- To add on-premises servers to a backend server group, you need to connect the on-premises data center to the VPC where the load balancer is running through Direct Connect or VPN. For details about how to connect on-premises data centers to the cloud, see the Direct Connect User Guide or Virtual Private Network User Guide.
Figure 1 Routing requests to cloud and on-premises servers
Prerequisites- A dedicated load balancer has been created.
- A listener has been added to the load balancer.
- VPC routes have been correctly configured to make backend servers accessible. IP as backend servers can be in a VPC connected using a VPC peering connection, or in an on-premises data center connected using a Direct Connect or VPN connection.
- Enabling IP as a Backend- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the Load Balancers page, locate the load balancer and click its name.
- On the Basic Information tab page, click Enable next to IP as a Backend.
- Click OK.
+ Constraints and LimitationsWhen you add IP as backend servers, note the following:
+ - IP as a backend cannot be disabled after it is enabled.
- If you do not enable the function when you create a load balancer, you can still enable it on the Summary page of the load balancer.
- IP as backend servers must use IPv4 addresses.
- If you enable IP as a backend for a load balancer, you can add only TCP, HTTP, and HTTPS listeners to the load balancer.
- The subnet where the load balancer works must have sufficient IP addresses. Otherwise, IP as backend servers cannot be added. You can add more subnets for more IP addresses on the Summary page of the load balancer.
- Security group rules of IP as backend servers must allow traffic from the subnet of the load balancer. Otherwise, health checks will fail.
- Adding IP as Backend Servers- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the Load Balancers page, locate the load balancer that you have created and click its name.
- In the Backend Server Groups tab, locate the backend server group and click its name.
- In the Basic Information area on the right, click IP as Backend Servers.
- Click Add IP as Backend Server and set the IP address, backend port, and weight.
 Ensure that the IP addresses of the servers are reachable and the backend ports are actually used by backend servers. Otherwise, the backend servers will be considered unhealthy.
+ Enabling IP as a Backend- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the Load Balancers page, locate the load balancer and click its name.
- On the Summary tab page, click Enable next to IP as a Backend.
- Click OK.
+
+
diff --git a/docs/elb/umn/elb_ug_hd_0006.html b/docs/elb/umn/elb_ug_hd_0006.html
index 10f5baf3..83fd3956 100644
--- a/docs/elb/umn/elb_ug_hd_0006.html
+++ b/docs/elb/umn/elb_ug_hd_0006.html
@@ -9,7 +9,8 @@
Prerequisites- You have created a dedicated load balancer.
- You have added an HTTP or HTTPS listener to the dedicated load balancer.
- Procedure- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the Load Balancers page, locate the dedicated load balancer that you have created and click its name.
- On the Backend Server Groups tab page, click Add Backend Server Group.
- Enable Slow Start and set the slow start duration. Set other parameters based on service requirements.
- Click OK.
+ Procedure- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the Load Balancers page, locate the dedicated load balancer that you have created and click its name.
- On the Backend Server Groups tab page, click Add Backend Server Group.
- Enable Slow Start and set the slow start duration. Set other parameters based on service requirements.
+
- Click OK.
diff --git a/docs/elb/umn/elb_ug_hd_0007.html b/docs/elb/umn/elb_ug_hd_0007.html
index ec90be0d..95f80b50 100644
--- a/docs/elb/umn/elb_ug_hd_0007.html
+++ b/docs/elb/umn/elb_ug_hd_0007.html
@@ -4,16 +4,52 @@
ScenariosWhen you add a backend server to a backend server group, ensure that the rules of the security group that containing the backend server allows access from the VPC where the backend server resides, and that the destination port is that used by the backend server. You also need to configure the protocol and port used for health checks. If you use UDP for health checks, configure inbound rules to allow ICMP traffic. Otherwise, health checks cannot be performed on the added backend server.
If you have no VPCs when creating a server, the system will automatically create a VPC with default security rules. Default security group rules allow only communications among the servers in the VPC. You also need to configure inbound rules to enable the load balancer to communicate with these servers over the frontend port and health check port.
- If IP as a Backend is not enabled for the dedicated load balancer that has a TCP or UDP listener, security group rules and network ACL rules will not take effect. To control traffic to backend servers, you can use access control to limit which IP addresses are allowed to access the listener. Learn how to configure access control.
+ If the load balancer has a TCP or UDP listener and IP as a backend is disabled, security group rules and firewall rules will not take effect. To control traffic to backend servers, you can use access control to limit which IP addresses are allowed to access the listener. Learn how to configure access control.
Procedure- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on
 in the upper left corner to display Service List and choose Computing > Elastic Cloud Server. - In the ECS list, locate the ECS and click its name.
The ECS details page is displayed.
- - Click Security Groups, locate the security group, and view security group rules.
- Click the security group rule ID or Modify Security Group Rule. The security group details page is displayed.
- Under Inbound Rules, click Add Rule.
TCP, HTTP, or HTTPS listeners
-- If the health check port is not the one used by each backend server, add an inbound rule to allow TCP traffic over the health check port and the ports used by backend servers.
- If you do not specify a health check port, add inbound rules to allow TCP traffic over the ports used by backend servers.
- To ensure normal health checks, ensure that security group rules allow traffic from the CIDR block of the subnet where the load balancer resides and traffic from the health check port and from the ports used by backend servers.
-UDP listeners
-- If the health check port is not the one used by each backend server, add an inbound rule to allow UDP traffic over the health check port and the ports used by backend servers.
- If you do not specify a health check port, add inbound rules to allow UDP traffic over the ports used by backend servers.
- To ensure normal health checks, ensure that security group rules allow traffic from the CIDR block of the subnet where the load balancer resides and traffic from the health check port and from the ports used by backend servers.
- You need also to add an inbound rule to allow ICMP traffic.
+ - Click Security Groups, locate the security group, and view security group rules.
- Click the security group rule ID or Modify Security Group Rule. The security group details page is displayed.
- On the Inbound Rules tab page, click Add Rule. Configure an inbound rule based on Table 1.
+
Table 1 Security group rulesBackend Protocol
+ |
+Policy
+ |
+Protocol & Port
+ |
+Source IP Address
+ |
+
|---|
+
+HTTP or HTTPS
+ |
+Allow
+ |
+Protocol: TCP
+Port: the port used by the backend server and health check port
+ |
+Backend subnet of the load balancer
+ |
+
+TCP
+ |
+Allow
+ |
+Protocol: TCP
+Port: health check port
+ |
+
+UDP
+ |
+Allow
+ |
+Protocol: UDP and ICMP
+Port: health check port
+ |
+
+
+
+ - Click OK.
- Configuring Firewall RulesTo control traffic in and out of a subnet, you can associate a firewall with the subnet. Similar to security groups, firewalls control access to subnets and add an additional layer of defense to your subnets. Default firewall rules reject all inbound and outbound traffic. If the subnet of a load balancer or associated backend servers has a firewall associated, the load balancer cannot receive traffic from the Internet or route traffic to backend servers, and backend servers cannot receive traffic from and respond to the load balancer.
+ Configuring Firewall RulesTo control traffic in and out of a subnet, you can associate a firewall with the subnet. Similar to security groups, firewall rules control access to subnets and add an additional layer of defense to your subnets. Default firewall rules reject all inbound and outbound traffic. If the subnet of a load balancer or associated backend servers has a firewall associated, the load balancer cannot receive traffic from the Internet or route traffic to backend servers, and backend servers cannot receive traffic from and respond to the load balancer.
Configure an inbound firewall rule to allow traffic from the VPC where the load balancer works to backend servers.
- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Click
 in the upper left corner of the page and choose Network > Virtual Private Cloud. - In the navigation pane on the left, choose Access Control > Firewall.
- In the firewall list, click the name of the firewall to switch to the page showing its details.
- On the Inbound Rules or Outbound Rules tab page, click Add Rule to add a rule.
- Action: Select Allow.
- Protocol: The protocol must be the same as the one you selected for the listener.
- Source: Set it to the VPC CIDR block.
- Source Port Range: Select a port range.
- Destination: If you keep the default value, 0.0.0.0/0, traffic will be allowed for all destination IP addresses.
- Destination Port Range: Select a port range.
- (Optional) Description: Describe the firewall rule.
- Click OK.
diff --git a/docs/elb/umn/elb_ug_hd_0008.html b/docs/elb/umn/elb_ug_hd_0008.html
index 6a3e7487..d1852ede 100644
--- a/docs/elb/umn/elb_ug_hd_0008.html
+++ b/docs/elb/umn/elb_ug_hd_0008.html
@@ -10,7 +10,7 @@
Weights do not take effect even if they are not 0, and requests from the same IP address are routed to the same backend server.
-
diff --git a/docs/elb/umn/elb_ug_ip_0000.html b/docs/elb/umn/elb_ug_ip_0000.html
index 5464e477..0fc4e62d 100644
--- a/docs/elb/umn/elb_ug_ip_0000.html
+++ b/docs/elb/umn/elb_ug_ip_0000.html
@@ -7,7 +7,7 @@
This function is available in the eu-de region, but unavailable in the eu-nl region.
- Creating an IP Address Group- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- In the navigation pane on the left, choose IP Address Groups. On the displayed page, click Create IP Address Group.
- Configure the parameters based on Table 1.
+
Creating an IP Address Group- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- In the navigation pane on the left, choose IP Address Groups. On the displayed page, click Create IP Address Group.
- Configure the parameters based on Table 1.
Table 1 Parameter descriptionParameter
|
Description
@@ -46,12 +46,12 @@
- Click OK.
-Modifying an IP Address Group - Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the IP Address Groups page, locate the IP address group, and click Modify in the Operation column.
- Modify the parameters based on Table 2.
-
Table 2 Parameters required for creating an IP address groupParameter
+Modifying an IP Address Group - Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the IP Address Groups page, locate the IP address group, and click Modify in the Operation column.
- Modify the parameters based on Table 2.
+
Table 2 Parameters required for creating an IP address groupParameter
|
-Description
+ | Description
|
-Example Value
+ | Example Value
|
|---|
@@ -86,7 +86,7 @@
- Click OK.
Deleting an IP Address GroupIf you no longer need an IP address group, you can delete it. If an IP address group has been associated with a listener, disassociate the IP address group from the listener before the deletion.
- - Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the IP Address Groups page, locate the IP address group, and click Delete in the Operation column.
- Click Yes.
+ - Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- On the IP Address Groups page, locate the IP address group, and click Delete in the Operation column.
- Click Yes.
≥ 0 bit/s
|
-- Shared load balancer
- Shared load balancer - listener
+ | - Shared load balancer
- Shared load balancer - listener
|
1 minute
|
@@ -227,7 +227,7 @@
≥ 0/second
|
-- Dedicated load balancer
- Shared load balancer
+ | - Dedicated load balancer
- Shared load balancer
|
1 minute
|
@@ -372,7 +372,6 @@
Ratio of the bandwidth that the monitored object uses to return response to clients over HTTP and HTTPS, to the maximum outbound bandwidth allowed
Unit: percent (%)
-Inbound bandwidth usage <100 %
CAUTION: If the inbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the inbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed.
|
@@ -385,7 +384,6 @@
Ratio of the bandwidth that the monitored object uses to return response to clients over HTTP and HTTPS, to the maximum outbound bandwidth allowed
Unit: percent (%)
-Outbound bandwidth usage <100 %
CAUTION: If the outbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the outbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed.
|
@@ -432,7 +430,6 @@
Ratio of the bandwidth that the monitored object uses to receive requests from clients over TCP and UDP, to the maximum inbound bandwidth allowed
Unit: percent (%)
-Inbound bandwidth usage <100 %
CAUTION: If the inbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the inbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed.
|
@@ -445,7 +442,6 @@
Ratio of the bandwidth that the monitored object uses to return response to clients over TCP and UDP, to the maximum outbound bandwidth allowed
Unit: percent (%)
-Outbound bandwidth usage <100 %
CAUTION: If the outbound bandwidth usage reaches 100%, the load balancer performance has reached the upper limit. If the outbound bandwidth keeps higher than the bandwidth that the load balancer can provide, the service availability cannot be guaranteed.
|
diff --git a/docs/elb/umn/elb_ug_jk_0002.html b/docs/elb/umn/elb_ug_jk_0002.html
index 4eb8de52..03ae0c8f 100644
--- a/docs/elb/umn/elb_ug_jk_0002.html
+++ b/docs/elb/umn/elb_ug_jk_0002.html
@@ -1,7 +1,7 @@
Setting an Alarm Rule
-You can add, modify, and delete alarm rules. For details, see the .
+ You can add, modify, and delete alarm rules. For details, see the Cloud Eye User Guide.
diff --git a/docs/elb/umn/elb_ug_jk_0003.html b/docs/elb/umn/elb_ug_jk_0003.html
index 02e548a9..de373bd9 100644
--- a/docs/elb/umn/elb_ug_jk_0003.html
+++ b/docs/elb/umn/elb_ug_jk_0003.html
@@ -3,7 +3,7 @@
Creating an Alarm Rule
- Log in to the management console.
- Under Management & Deployment, click Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- On the displayed Alarm Rules page, click Create Alarm Rule.
The following describes how to create an alarm rule for a load balancer. - Resource Type: Select Elastic Load Balancing.
- For Dimension, select Elastic Load Balancers. In the following operations, a load balancer is used as an example.
- Configure other parameters as required and then click Create.
Once the alarm rule is created and the notification function has been enabled, the system automatically sends you a notification when an alarm is generated. For more information about alarm rules of load balancers and listeners, see the Cloud Eye User Guide.
+ Once the alarm rule is created and the notification function has been enabled, the system automatically sends you a notification when an alarm is generated. For more information about alarm rules of load balancers and listeners, see the Cloud Eye User Guide.
diff --git a/docs/elb/umn/elb_ug_jk_0005.html b/docs/elb/umn/elb_ug_jk_0005.html
index 2a4fd0b6..e355dcf5 100644
--- a/docs/elb/umn/elb_ug_jk_0005.html
+++ b/docs/elb/umn/elb_ug_jk_0005.html
@@ -1,7 +1,7 @@
Viewing Metrics
- ScenariosCloud Eye provided by the public cloud platform monitors the running statuses of load balancers.
+ ScenariosCloud Eye provided by the public cloud platform monitors the running statuses of load balancers.
You can view the metrics of each load balancer on the ELB console or the Cloud Eye console.
The transmission of monitoring data takes a while, so the status of each load balancer displayed on the Cloud Eye dashboard is not its real-time status. For a newly created load balancer or a newly added listener, you need to wait for about 5 minutes to 10 minutes before you can view its metrics.
diff --git a/docs/elb/umn/elb_ug_jl_0000.html b/docs/elb/umn/elb_ug_jl_0000.html
index 403fd932..3c83a7a0 100644
--- a/docs/elb/umn/elb_ug_jl_0000.html
+++ b/docs/elb/umn/elb_ug_jl_0000.html
@@ -8,11 +8,20 @@
- 2023-02-09
+ | 2023-04-06
+ |
+Modified the following content:
+Added:
+
+Updated:
+
+ |
+
+2023-02-09
|
Modified the following content:
Added:
-
+
Updated:
Deleted:
@@ -64,13 +73,13 @@
| Modified the following content:
Added the following sections:
-Updated How Can I Transfer the IP Address of a Client?.
+Updated How Can I Transfer the IP Address of a Client?
|
2022-02-24
|
Modified the following content:
-Added Does ELB Have Restrictions on the File Upload Speed and Size?.
+Added Does ELB Have Restrictions on the File Upload Speed and Size?
|
2022-02-11
@@ -118,13 +127,13 @@
| 2021-05-20
|
Modified the following content:
-Added the constraints on binding EIPs to dedicated load balancers in the eu-de region in Table 1.
+Added the constraints on binding EIPs to dedicated load balancers in the eu-de region in Table 1.
|
2021-04-08
|
Modified the following content:
-- Added descriptions about classic load balancers to section "Differences Between Enhanced and Classic Load Balancers", How ELB Works, Load Balancing Algorithms, Sticky Session, HTTP Redirection to HTTPS, Is an EIP Assigned Exclusively to a Load Balancer?, What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?, How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?, and What Types of Sticky Sessions Does ELB Support?.
- Changed Create Enhanced Load Balancer to Create Elastic Load Balancer in Using Shared Load Balancers (Entry Level).
- Deleted the procedure for adding a listener to a classic load balancer in Adding a Listener.
- Deleted the procedure and parameter descriptions for creating classic load balancers in Modifying or Deleting a Listener, Configuring Security Group Rules for Backend Servers (Shared Load Balancers), Configuring a Health Check, Disabling a Health Check, Tag, and How Do I Troubleshoot an Unhealthy Backend Server?
- Deleted section "Adding or Removing Backend Servers (Classic Load Balancers)".
- Added Adding or Removing Backend Servers (Dedicated Load Balancers).
+- Added descriptions about classic load balancers to section "Differences Between Enhanced and Classic Load Balancers", How ELB Works, Load Balancing Algorithms, Sticky Session, HTTP Redirection to HTTPS, Is an EIP Assigned Exclusively to a Load Balancer?, What Are the Relationships Between Load Balancing Algorithms and Sticky Session Types?, How Does ELB Perform UDP Health Checks? What Are the Precautions for UDP Health Checks?, and What Types of Sticky Sessions Does ELB Support?
- Changed Create Enhanced Load Balancer to Create Elastic Load Balancer in Using Shared Load Balancers (Entry Level).
- Deleted the procedure for adding a listener to a classic load balancer in Adding a Listener.
- Deleted the procedure and parameter descriptions for creating classic load balancers in Modifying or Deleting a Listener, Configuring Security Group Rules for Backend Servers (Shared Load Balancers), Configuring a Health Check, Disabling a Health Check, Tag, and How Do I Troubleshoot an Unhealthy Backend Server?
- Deleted section "Adding or Removing Backend Servers (Classic Load Balancers)".
- Added Adding or Removing Backend Servers (Dedicated Load Balancers).
|
2021-03-02
diff --git a/docs/elb/umn/elb_ug_jt_0002.html b/docs/elb/umn/elb_ug_jt_0002.html
index 735d024f..f14e1c29 100644
--- a/docs/elb/umn/elb_ug_jt_0002.html
+++ b/docs/elb/umn/elb_ug_jt_0002.html
@@ -36,23 +36,30 @@
Backend Protocols and PortsBackend protocols and ports are used by backend servers to receive requests from load balancers. If Windows servers have Internet Information Services (IIS) installed, the default backend protocol and port are HTTP and 80.
- Table 2 Backend protocols and portsProtocol
+Table 2 Backend protocols and portsProtocol
|
-Port
+ | Port
|
|---|
TCP
|
-Backend servers can use the same ports. The port number ranges from 1 to 65535.
+ | Backend servers can use the same ports. The port number ranges from 1 to 65535.
The following are some commonly-used protocols and port numbers:
TCP/80
HTTP/443
+
+
+
+
|
UDP
|
+QUIC
+ |
+
HTTP
|
diff --git a/docs/elb/umn/elb_ug_jt_0003.html b/docs/elb/umn/elb_ug_jt_0003.html
index 075f4ffd..4d3e6c54 100644
--- a/docs/elb/umn/elb_ug_jt_0003.html
+++ b/docs/elb/umn/elb_ug_jt_0003.html
@@ -2,17 +2,21 @@
Load Balancing Algorithms
Load balancers receive requests from clients and forward them to backend servers in one or more AZs. Each load balancer has at least a listener and a backend server. The load balancing algorithm you select when you add the listener determines how requests are distributed.
- Load Balancing AlgorithmsBoth dedicated and shared load balancers support weighted round robin, weighted least connections, and source IP hash.
+ Load Balancing AlgorithmsDedicated load balancers support four load balancing algorithms: weighted round robin, weighted least connections, source IP hash, and connection ID. Shared load balancers support three load balancing algorithms: weighted round robin, weighted least connections, and source IP hash.
- Weighted round robin: Requests are routed to backend servers using the round robin algorithm. Backend servers with higher weights receive proportionately more requests, whereas equal-weighted servers receive the same number of requests. This algorithm is often used for short connections, such as HTTP connections.
The following figure shows an example of how requests are distributed using the weighted round robin algorithm. Two backend servers are in the same AZ and have the same weight, and each server receives the same proportion of requests.
Figure 1 Traffic distribution using the weighted round robin algorithm
- Weighted least connections: In addition to the weight assigned to each server, the number of connections being processed by each backend server is also considered. Requests are routed to the server with the lowest connections-to-weight ratio. In addition to the number of connections, each server is assigned a weight based on its capacity. Requests are routed to the server with the lowest connections-to-weight ratio. This algorithm is often used for persistent connections, such as connections to a database.
The following figure shows an example of how requests are distributed using the weighted least connections algorithm. Two backend servers are in the same AZ and have the same weight, 100 connections have been established with backend server 01, and 50 connections have been connected with backend server 02. New requests are preferentially routed to backend server 02.
Figure 2 Traffic distribution using the weighted least connections algorithm
- Source IP hash: The source IP address of each request is calculated using the consistent hashing algorithm to obtain a unique hashing key, and all backend servers are numbered. The generated key is used to allocate the client to a particular server. This allows requests from different clients to be routed based on source IP addresses and ensures that a client is directed to the same server that it was using previously. This algorithm works well for TCP connections of load balancers that do not use cookies.
The following figure shows an example of how requests are distributed using the source IP hash algorithm. Two backend servers are in the same AZ and have the same weight. If backend server 01 has processed a request from IP address A, the load balancer will route new requests from IP address A to backend server 01.
Figure 3 Traffic distribution using the source IP hash algorithm
+ - Connection ID: The connection ID in the packet is calculated using the consistent hash algorithm to obtain a specific value, and backend servers are numbered. The generated value determines to which backend server the requests are routed. This allows requests with different connection IDs to be routed to different backend servers and ensures that requests with the same connection ID are routed to the same backend server. This algorithm applies to QUIC requests.
Currently, only dedicated load balancers support the Connection ID algorithm.
+
+Figure 4 shows an example of how requests are distributed using the connection ID algorithm. Two backend servers are in the same AZ and have the same weight. If backend server 01 has processed a request from client A, the load balancer will route new requests from client A to backend server 01.
+Figure 4 Traffic distribution using the connection ID algorithm
- Changing the Load Balancing Algorithm- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Locate the load balancer and click its name.
- Click Backend Server Groups and click
 on the right of the backend server group name. - Select a load balancing algorithm.
The modification will take effect immediately. The load balancer will establish new connections with the clients, and request routing over established connections will not be affected.
+
diff --git a/docs/elb/umn/elb_ug_jt_0004.html b/docs/elb/umn/elb_ug_jt_0004.html
index cca2a431..8102c3f3 100644
--- a/docs/elb/umn/elb_ug_jt_0004.html
+++ b/docs/elb/umn/elb_ug_jt_0004.html
@@ -6,7 +6,7 @@
Sticky sessions at Layer 4 are different from those at Layer 7.
PrerequisitesYou have selected Weighted round robin for Load Balancing Algorithm.
- Constraints and LimitationsIf you use Direct Connect, VPN, to access ELB, you must select Source IP hash as the load balancing algorithm and disable sticky sessions for ELB.
+ Constraints and LimitationsIf you use Direct Connect or VPN to access ELB, you must select Source IP hash as the load balancing algorithm and disable sticky sessions for ELB.
Differences Between Sticky Sessions at Layer 4 and Layer 7
Table 1 Sticky session comparisonOSI Layer
@@ -27,7 +27,7 @@
| Source IP address: The source IP address of each request is calculated using the consistent hashing algorithm to obtain a unique hash key, and all backend servers are numbered. The system allocates the client to a particular server based on the generated key. This enables requests from different clients to be routed and ensures that a client is directed to the same server that it was using previously.
|
-- Default: 20 minutes
- Maximum: 1 hour
- Range: 1 minute to 60 minutes
+ | - Default: 20 minutes
- Maximum: 60 minutes
- Range: 1 minute to 60 minutes
|
- Source IP addresses of the clients change.
- The session stickiness duration has been reached.
|
@@ -38,7 +38,7 @@
- Load balancer cookie: The load balancer generates a cookie after receiving a request from the client. All subsequent requests with the same cookie are then routed to the same backend server.
- Application cookie: The application deployed on the backend server generates a cookie after receiving the first request from the client. All requests with the same cookie generated by backend application are then routed to the same backend server.
|
-- Default: 20 minutes
- Maximum: 24 hours
- Range: 1 minute to 1,440 minutes
+ | - Default: 20 minutes
- Maximum: 1,440 minutes
- Range: 1 minute to 1,440 minutes
|
- If requests sent by the clients do not contain a cookie, sticky sessions will not take effect.
- The session stickiness duration has been reached.
|
@@ -49,7 +49,7 @@
Dedicated load balancers support two types of sticky session: Source IP address and Load balancer cookie.
Shared load balancers support three types of sticky session, including Source IP address, Load balancer cookie, and Application cookie.
-
-Adding a TCP Listener to a Dedicated Load Balancer- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Locate the load balancer and click its name.
- Under Listeners, click Add Listener. Configure the parameters based on Table 1.
+
Adding a TCP Listener to a Dedicated Load Balancer- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Locate the load balancer and click its name.
- Under Listeners, click Add Listener. Configure the parameters based on Table 1.
Table 1 Parameters for configuring a listenerParameter
|
Description
@@ -88,7 +88,7 @@
|
|---|
- Click Next: Configure Request Routing Policy. Table 2 describes the parameters for configuring a backend server group.
+
- Click Next: Configure Request Routing Policy. For details about how to configure a backend server group, see Table 2.
Table 2 Parameters for configuring a backend server groupParameter
|
Description
@@ -151,7 +151,7 @@
|
|---|
Stickiness Duration (min)
|
-Specifies the minutes that sticky sessions are maintained. You can enable sticky sessions only if you select Weighted round robin or Weighted least connections for Load Balancing Algorithm.
+ | Specifies the minutes that sticky sessions are maintained. You can enable sticky sessions only if you select Weighted round robin for Load Balancing Algorithm.
- Stickiness duration at Layer 4: 1 to 60
- Stickiness duration at Layer 7: 1 to 1440
|
20
@@ -251,7 +251,7 @@
- Click Next: Confirm.
- Confirm the configuration and click Submit.
-Adding a TCP Listener to a Shared Load Balancer- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Locate the load balancer and click its name.
- Under Listeners, click Add Listener. Configure the parameters based on Table 4.
+
Adding a TCP Listener to a Shared Load Balancer- Log in to the management console.
- In the upper left corner of the page, click and select the desired region and project.
- Hover on in the upper left corner to display Service List and choose Network > Elastic Load Balancing.
- Locate the load balancer and click its name.
- Under Listeners, click Add Listener. Configure the parameters based on Table 4.
|
|---|
|
|---|
|
|
|---|
|
|---|
|
