diff --git a/docs/elb/umn/ALL_META.TXT.json b/docs/elb/umn/ALL_META.TXT.json
index ac10baa4..3b327f13 100644
--- a/docs/elb/umn/ALL_META.TXT.json
+++ b/docs/elb/umn/ALL_META.TXT.json
@@ -173,17 +173,14 @@
"node_id":"en-us_topic_0287737145.xml",
"product_code":"elb",
"code":"9",
- "des":"Load balancers are available in different specifications. Choose the specifications that best meet your needs. If the traffic exceeds the selected specifications, new req",
+ "des":"When you create a dedicated load balancer, you can select elastic or fixed specifications based on your service requirements. Table 1 compares the two types of specificat",
"doc_type":"usermanual",
"kw":"Specifications of Dedicated Load Balancers,Service Overview,User Guide",
"search_title":"",
"metedata":[
{
"prodname":"elb",
- "documenttype":"usermanual",
- "IsMulti":"No",
- "opensource":"true;false",
- "IsBot":"Yes"
+ "documenttype":"usermanual"
}
],
"title":"Specifications of Dedicated Load Balancers",
diff --git a/docs/elb/umn/CLASS.TXT.json b/docs/elb/umn/CLASS.TXT.json
index 32a8f319..a0afd557 100644
--- a/docs/elb/umn/CLASS.TXT.json
+++ b/docs/elb/umn/CLASS.TXT.json
@@ -72,7 +72,7 @@
"code":"8"
},
{
- "desc":"Load balancers are available in different specifications. Choose the specifications that best meet your needs. If the traffic exceeds the selected specifications, new req",
+ "desc":"When you create a dedicated load balancer, you can select elastic or fixed specifications based on your service requirements. Table 1 compares the two types of specificat",
"product_code":"elb",
"title":"Specifications of Dedicated Load Balancers",
"uri":"en-us_topic_0287737145.html",
diff --git a/docs/elb/umn/elb_lb_000006.html b/docs/elb/umn/elb_lb_000006.html
index 4f3d2713..50599840 100644
--- a/docs/elb/umn/elb_lb_000006.html
+++ b/docs/elb/umn/elb_lb_000006.html
@@ -42,11 +42,13 @@
-
|
-Specifications
+ |
Specifications
|
-- Select either Application load balancing (HTTP/HTTPS) or Network load balancing (TCP/UDP) or both, and then select the desired specification. You can select only one specification for Application load balancing (HTTP/HTTPS) and Network load balancing (TCP/UDP), respectively. Select the desired specifications based on your service plan by referring to Specifications of Dedicated Load Balancers.
- For application load balancing, the number of IP addresses varies depending on the specification. You can view the number of IP addresses required by the load balancer in the advanced settings.
- The performance of load balancers varies depending on the selected specifications. You can evaluate the actual traffic and select appropriate specifications based on the key metrics.
+ | Select Elastic or Fixed.
+- Elastic specifications work well for fluctuating traffic, and you will be charged for how many LCUs you use.
- Fixed specifications are suitable for stable traffic, and you will be charged for the specifications you select.
+Select either Application load balancing (HTTP/HTTPS) or Network load balancing (TCP/UDP) or both, and then select the desired specification. You can select only one specification for Application load balancing (HTTP/HTTPS) and Network load balancing (TCP/UDP), respectively. Select the desired specifications based on your service size by referring to Specifications of Dedicated Load Balancers.
|
-Medium II
+ | Elastic
|
Name
diff --git a/docs/elb/umn/elb_ug_jk_0001.html b/docs/elb/umn/elb_ug_jk_0001.html
index 3b810cc3..41a2ced4 100644
--- a/docs/elb/umn/elb_ug_jk_0001.html
+++ b/docs/elb/umn/elb_ug_jk_0001.html
@@ -27,7 +27,7 @@
|
Load balancing at Layer 4: total number of TCP and UDP connections from the monitored object to backend servers
Load balancing at Layer 7: total number of TCP connections from the clients to the monitored object
-Unit: N/A
+Unit: Count
|
≥ 0
|
@@ -43,7 +43,7 @@
Number of TCP and UDP connections in the ESTABLISHED state between the monitored object and backend servers
You can run the following command to view the connections (both Windows and Linux servers):
netstat -an
-Unit: N/A
+Unit: Count
|
≥ 0
|
@@ -55,7 +55,7 @@
Number of TCP connections between the monitored object and backend servers except those in the ESTABLISHED state
You can run the following command to view the connections (both Windows and Linux servers):
netstat -an
-Unit: N/A
+Unit: Count
|
≥ 0
|
@@ -115,7 +115,7 @@
Unhealthy Servers
|
Number of unhealthy backend servers associated with the monitored object
-Unit: N/A
+Unit: Count
|
≥ 0
|
@@ -129,7 +129,7 @@
Healthy Servers
|
Number of healthy backend servers associated with the monitored object
-Unit: N/A
+Unit: Count
|
≥ 0
|
@@ -144,21 +144,8 @@
≥ 0/second
|
-
-
-
-
-
-
|
1 minute
-
-
-
-
-
-
-
|
m21_client_rps
@@ -190,7 +177,7 @@
|
≥ 0 bit/s
|
-- Shared load balancer
- Shared load balancer - listener
+ | - Load balancer
- Load balancer - listener
|
1 minute
|
@@ -358,6 +345,58 @@
≥ 0 ms
|
+m1a_l7_upstream_rt_max
+ |
+Maximum Server Response Time
+ |
+Maximum response time of backend servers (This metric is available only when the frontend protocol is HTTP or HTTPS.)
+The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server.
+Unit: ms
+ |
+≥ 0 ms
+ |
+- Dedicated load balancer
- Shared load balancer
- Dedicated load balancer - listener
- Shared load balancer - listener
+ |
+1 minute
+ |
+
+m1b_l7_upstream_rt_min
+ |
+Minimum Server Response Time
+ |
+Maximum response time of backend servers (This metric is available only when the frontend protocol is HTTP or HTTPS.)
+The response time starts when the monitored object routes the requests to the backend server and ends when the monitored object receives a response from the backend server.
+Unit: ms
+ |
+≥ 0 ms
+ |
+
+m1c_l7_rt_max
+ |
+Maximum Layer-7 Response Time
+ |
+Maximum response time of the monitored object. (This metric is available only when the frontend protocol is HTTP or HTTPS.)
+The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients.
+Unit: ms
+ |
+≥ 0 ms
+ |
+- Dedicated load balancer
- Shared load balancer
- Dedicated load balancer - listener
- Shared load balancer - listener
+ |
+1 minute
+ |
+
+m1d_l7_rt_min
+ |
+Minimum Layer-7 Response Time
+ |
+Minimum response time of the monitored object. (This metric is available only when the frontend protocol is HTTP or HTTPS.)
+The response time starts when the monitored object receives requests from the clients and ends when it returns all responses to the clients.
+Unit: ms
+ |
+≥ 0 ms
+ |
+
l7_con_usage
|
Layer-7 Concurrent Connection Usage
@@ -376,7 +415,7 @@
|
Layer-7 Inbound Bandwidth Usage
|
-Ratio of the bandwidth that the monitored object uses to receives requests from clients over HTTP and HTTPS, to the maximum inbound bandwidth allowed
+ | Ratio of the bandwidth that the monitored object uses to receive requests from clients over HTTP and HTTPS, to the maximum inbound bandwidth allowed
Unit: percent (%)
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.
@@ -434,7 +473,7 @@
|
Layer-4 Inbound Bandwidth Usage
|
-Ratio of the bandwidth that the monitored object uses to receives requests from clients over TCP and UDP, to the maximum inbound bandwidth allowed
+ | 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 (%)
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.
diff --git a/docs/elb/umn/elb_ug_jl_0000.html b/docs/elb/umn/elb_ug_jl_0000.html
index dafaf1d4..dba31a06 100644
--- a/docs/elb/umn/elb_ug_jl_0000.html
+++ b/docs/elb/umn/elb_ug_jl_0000.html
@@ -8,9 +8,14 @@
|
-2024-08-30
+ |
2024-09-26
|
-Modified the following sections:
+ | Introduced elastic specifications for dedicated load balancers.
+ |
+
+2024-08-30
+ |
+Modified the following content:
- An SNI certificate can have up to 100 domain names.
- SNI certificates of a dedicated load balancer's listener can have up to 200 domain names.
- SNI certificates of a shared load balancer's listener can have up to 30 domain names.
|
diff --git a/docs/elb/umn/en-us_topic_0150301848.html b/docs/elb/umn/en-us_topic_0150301848.html
index 8a943ddd..21542f62 100644
--- a/docs/elb/umn/en-us_topic_0150301848.html
+++ b/docs/elb/umn/en-us_topic_0150301848.html
@@ -6,10 +6,10 @@
- ELB displays operations data, such as access logs, on the LTS console. Do not transmit private or sensitive data through fields in access logs. Encrypt your sensitive data if necessary.
- Currently, access logging is not supported in the eu-nl region.
Notes and Constraints
- Access logging can be configured only for application (Layer 7) load balancers.
- The access logs do not contain requests whose return code is 400 Bad Request. This is because such requests do not comply with HTTP specification and cannot be processed properly.
+
Constraints
- Access logging can be configured only for load balancers that have HTTP or HTTPS listeners.
- The access logs do not contain requests whose return code is 400 Bad Request. This is because such requests do not comply with HTTP specification and cannot be processed properly.
Flowchart
Figure 1 Process for locating an unhealthy backend server
@@ -249,7 +249,7 @@ $pool_name "$member_name" $tenant_id $eip_address:$eip_port "$upstream_addr_priv
pool_name
|
-Backend server group name in the format of pool_backend server group ID
+ | Backend server group name in the format of pool_backend server group ID or pool_backend server group ID*load balancer ID.
|
String
|
@@ -258,7 +258,7 @@ $pool_name "$member_name" $tenant_id $eip_address:$eip_port "$upstream_addr_priv
member_name
|
-Backend server name in the format of member_server ID. This field is not supported yet. There may be multiple values separated by commas and spaces, and the value can be member_id) or -.
+ | Backend server name in the format of member_server ID. This field is not supported yet. There may be multiple values separated by commas and spaces, and each value is a member ID (member_id) or -.
|
String
|
diff --git a/docs/elb/umn/en-us_topic_0287737145.html b/docs/elb/umn/en-us_topic_0287737145.html
index 10db3c48..1af75d29 100644
--- a/docs/elb/umn/en-us_topic_0287737145.html
+++ b/docs/elb/umn/en-us_topic_0287737145.html
@@ -1,270 +1,412 @@
Specifications of Dedicated Load Balancers
-Load balancers are available in different specifications. Choose the specifications that best meet your needs. If the traffic exceeds the selected specifications, new requests will be discarded.
-
- Maximum concurrent connections
Indicates the maximum number of concurrent connections that a load balancer can handle. If the number reaches the maximum connections that defined in the specification, new requests will be discarded to ensure the performance of the established connections.
- - Connections per second (CPS)
Indicates the number of new connections that a load balancer can establish per second. If the number reaches the CPS that defined in the specification, new requests will be discarded to ensure the performance of established connections.
-HTTPS listeners need to create SSL handshakes to establish connections with clients, and such SSL handshakes occupy more system resources than HTTP listeners. For example, a small I application load balancer can establish 2,000 new HTTP connections per second but only 200 new HTTPS connections per second.
-For a small I application load balancer:
-- If you only add an HTTP listener, the load balancer can establish up to 2,000 new HTTP connections.
- If you only add an HTTPS listener, the load balancer can establish up to 200 new HTTPS connections.
- If you add an HTTPS listener and an HTTP listener, the new connections are calculated using the following formula:
New connections = New HTTP connections + New HTTPS connections x Ratio of HTTP connections to HTTPS connections
-For a small I application load balancer, the ratio of HTTP connections to HTTPS connections is 10. For details, see Table 1.
+When you create a dedicated load balancer, you can select elastic or fixed specifications based on your service requirements. Table 1 compares the two types of specifications.
+
If the traffic exceeds the selected specifications, new requests will be discarded. Select the specifications based on your service requirements.
-
Table 1 New connections that a small I application load balancer can establishParameter
+Table 1 Specifications comparisonItem
|
-Scenario 1
+ | Elastic
|
-Scenario 2
+ | Fixed
|
|---|
-New HTTP connections
+ | Application scenarios
|
-1,000
+ | - For fluctuating traffic
- When you need to use resources temporarily and for urgent purposes
|
-1,000
+ | - For stable traffic
- When you need to use resources for a long term
|
-New HTTPS connections
+ | Network (TCP/UDP) load balancer performance
|
-50
+ | The performance multiplies as the number of AZs increases. Table 3 shows the maximum performance in an AZ.
|
-150
+ | The performance multiplies as the number of AZs increases. Table 6 shows the maximum performance in an AZ.
|
-New HTTP and HTTPS connections
+ | Application (HTTP/HTTPS) load balancer performance
|
-1,000 + 50 x 10 = 1,500
+ | The performance multiplies as the number of AZs increases. Table 3 shows the maximum performance in an AZ.
|
-1,000 + 150 x 10 = 2,500
+ | The performance multiplies as the number of AZs increases. Table 7 shows the maximum performance in an AZ.
|
-Description
+ | Billing items
|
-The new connections do not reach the CPS (HTTP) defined in Table 3, and new requests can be properly routed.
+ |
|
-The new connections exceed the CPS (HTTP) defined in Table 3, and new requests will be discarded.
+ | LCU
+ |
+
+Capabilities
+ |
+Same
|
Details in the Table 1 are for reference only.
+ Elastic SpecificationsIf your service traffic fluctuates greatly, you can choose elastic specifications and select network load balancing (TCP/UDP/TLS) or application load balancing (HTTP/HTTPS), or both that best meet your service needs.
+ The listener protocol must match the load balancing type. For example, if you select application load balancing (HTTP/HTTPS), you can only add an HTTP or HTTPS listener to this load balancer.
+
+ Table 2 describes the dimensions about elastic specifications. When your traffic exceeds the specifications defined in Table 3, new requests will be discarded.
+
+ Table 2 Elastic specification dimensionsMaximum Connections
+ |
+Indicates the maximum number of concurrent connections that a load balancer can handle per minute. If the number reaches the maximum connections that is defined in the elastic specifications, new requests will be discarded to ensure the performance of established connections.
+ |
+
|---|
+Connection Per Second (CPS)
+ |
+Indicates the number of new connections that a load balancer can establish per second. If the number reaches the CPS that is defined in the elastic specifications, new requests will be discarded to ensure the performance of established connections.
+ |
+
|---|
+Query Per Second (QPS)
+ |
+Indicates the number of HTTP or HTTPS requests sent to a backend server per second. If the QPS reaches that is defined in the elastic specifications, new requests will be discarded to ensure the performance of established connections.
+ |
+
|---|
+Bandwidth (Mbit/s)
+ |
+Indicates the maximum amount of data that can be transmitted over a connection per second.
+ |
+
|---|
+
+
+
+
+ Table 3 Maximum elastic specificationsProtocol
+ |
+Maximum Connections
+ |
+CPS
+ |
+QPS
+ |
+Bandwidth (Mbit/s)
+ |
+
|---|
+
+Network load balancing (TCP/UDP)
+ |
+20,000,000
+ |
+400,000
+ |
+N/A
+ |
+10,000
+ |
+
+Application load balancing (HTTP)
+ |
+8,000,000
+ |
+80,000
+ |
+160,000
+ |
+10,000
+ |
+
+Application load balancing (HTTPS)
+ |
+8,000,000
+ |
+80,000
+ |
+160,000
+ |
+10,000
+ |
+
+
+
+
+
+ Fixed SpecificationsLoad balancers are available in different fixed specifications. Choose the specifications that best meet your needs. When your traffic exceeds what defined in your selected specifications, new requests will be discarded. Each specification has the following dimensions.
+
+ Table 4 Fixed specification dimensionsMaximum Connections
+ |
+Indicates the maximum number of concurrent connections that a load balancer can handle per minute. If the number reaches the maximum connections that is defined in your selected fixed specifications, new requests will be discarded to ensure the performance of existing connections.
+ |
+
|---|
+CPS
+ |
+Indicates the number of new connections that a load balancer can establish per second. If the number reaches the CPS that is defined in your selected fixed specifications, new requests will be discarded to ensure the performance of established connections.
+HTTPS listeners need to create SSL handshakes to establish connections with clients, and such SSL handshakes occupy more system resources than HTTP listeners. For example, a small I application load balancer can establish 2,000 new HTTP connections per second but only 200 new HTTPS connections per second. For details, see Table 5.
+ |
+
|---|
+QPS
+ |
+Indicates the number of HTTP or HTTPS requests sent to a backend server per second. If the QPS reaches that is defined in your selected fixed specifications, new requests will be discarded to ensure the performance of established connections.
+ |
+
|---|
+Bandwidth (Mbit/s)
+ |
+Indicates the maximum amount of data that can be transmitted over a connection per second.
+ |
+
|---|
+
+
+
+
+ For a small I application load balancer:
+ - If you only add an HTTP listener, the load balancer can establish up to 2,000 new HTTP connections.
- If you only add an HTTPS listener, the load balancer can establish up to 200 new HTTPS connections.
- If you add an HTTPS listener and an HTTP listener, the new connections are calculated using the following formula:
New connections = New HTTP connections + New HTTPS connections x Ratio of HTTP connections to HTTPS connections
+For a small I application load balancer, the ratio of HTTP connections to HTTPS connections is 10. For details, see Table 5.
+
+Table 5 New connections that a small I application load balancer can establishParameter
+ |
+Scenario 1
+ |
+Scenario 2
+ |
+
|---|
+
+New HTTP connections
+ |
+1,000
+ |
+1,000
+ |
+
+New HTTPS connections
+ |
+50
+ |
+150
+ |
+
+New HTTP and HTTPS connections
+ |
+1,000 + 50 x 10 = 1,500
+ |
+1,000 + 150 x 10 = 2,500
+ |
+
+Description
+ |
+- The new connections do not reach the CPS (HTTP) that a small I application load balancer can handle, so new requests can be properly routed.
+ |
+- The new connections exceed the CPS (HTTP) that a small I application load balancer can handle, so new requests will be discarded.
+ |
+
+
+
+ Details in the Table 5 are for reference only.
- - Queries per second (QPS)
Indicates the number of HTTP or HTTPS requests sent to a backend server per second. If the QPS reaches that defined in the specification, new requests will be discarded to ensure the performance of established connections.
- - Bandwidth (Mbit/s)
Indicates the maximum amount of data that can be transmitted over a load balancer per second.
-
- Table 2 and Table 3 list the specifications of dedicated load balancers.
-
+ Table 6 and Table 7 list the fixed specifications of dedicated load balancers.
- Table 2 Specifications for network load balancing (TCP/UDP)Type
+Table 6 Fixed specifications for a network load balancer (TCP/UDP)Type
|
-Maximum Concurrent Connections
+ | Maximum Connections
|
-CPS
+ | CPS
|
-Bandwidth (Mbit/s)
+ | Bandwidth (Mbit/s)
|
-LCUs in an AZ
+ | LCUs in an AZ
|
|---|
-Small I
+ | Small I
|
-500,000
+ | 500,000
|
-10,000
+ | 10,000
|
-50
+ | 50
|
-10
+ | 10
|
-Small II
+ | Small II
|
-1,000,000
+ | 1,000,000
|
-20,000
+ | 20,000
|
-100
+ | 100
|
-20
+ | 20
|
-Medium I
+ | Medium I
|
-2,000,000
+ | 2,000,000
|
-40,000
+ | 40,000
|
-200
+ | 200
|
-40
+ | 40
|
-Medium II
+ | Medium II
|
-4,000,000
+ | 4,000,000
|
-80,000
+ | 80,000
|
-400
+ | 400
|
-80
+ | 80
|
-Large I
+ | Large I
|
-10,000,000
+ | 10,000,000
|
-200,000
+ | 200,000
|
-1,000
+ | 1,000
|
-200
+ | 200
|
-Large II
+ | Large II
|
-20,000,000
+ | 20,000,000
|
-400,000
+ | 400,000
|
-2,000
+ | 2,000
|
-400
+ | 400
|
Table 3 Specifications for application load balancing (HTTP/HTTPS)Type
+Table 7 Fixed specifications for an application load balancer (HTTP/HTTPS)Type
|
-Maximum Concurrent Connections
+ | Maximum Connections
|
-CPS (HTTP)
+ | CPS (HTTP)
|
-CPS (HTTPS)
+ | CPS (HTTPS)
|
-QPS (HTTP)
+ | QPS (HTTP)
|
-QPS (HTTPS)
+ | QPS (HTTPS)
|
-Bandwidth (Mbit/s)
+ | Bandwidth (Mbit/s)
|
-Number of LCUs in an AZ
+ | LCUs in an AZ
|
|---|
-Small I
+ | Small I
|
-200,000
+ | 200,000
|
-2,000
+ | 2,000
|
-200
+ | 200
|
-4,000
+ | 4,000
|
-2,000
+ | 2,000
|
-50
+ | 50
|
-10
+ | 10
|
-Small II
+ | Small II
|
-400,000
+ | 400,000
|
-4,000
+ | 4,000
|
-400
+ | 400
|
-8,000
+ | 8,000
|
-4,000
+ | 4,000
|
-100
+ | 100
|
-20
+ | 20
|
-Medium I
+ | Medium I
|
-800,000
+ | 800,000
|
-8,000
+ | 8,000
|
-800
+ | 800
|
-16,000
+ | 16,000
|
-8,000
+ | 8,000
|
-200
+ | 200
|
-40
+ | 40
|
-Medium II
+ | Medium II
|
-2,000,000
+ | 2,000,000
|
-20,000
+ | 20,000
|
-2,000
+ | 2,000
|
-40,000
+ | 40,000
|
-20,000
+ | 20,000
|
-400
+ | 400
|
-100
+ | 100
|
-Large I
+ | Large I
|
-4,000,000
+ | 4,000,000
|
-40,000
+ | 40,000
|
-4,000
+ | 4,000
|
-80,000
+ | 80,000
|
-40,000
+ | 40,000
|
-1,000
+ | 1,000
|
-200
+ | 200
|
-Large II
+ | Large II
|
-8,000,000
+ | 8,000,000
|
-80,000
+ | 80,000
|
-8,000
+ | 8,000
|
-160,000
+ | 160,000
|
-80,000
+ | 80,000
|
-2,000
+ | 2,000
|
-400
+ | 400
|
- If you add multiple listeners to a load balancer, the sum of QPS values of all listeners cannot exceed the QPS defined in each specification.
- The bandwidth is the upper limit of the inbound or the outbound traffic. For example, for small I load balancers, the inbound or outbound traffic cannot exceed 50 Mbit/s.
- The bandwidth included in each specification is the maximum bandwidth provided by ELB. If the maximum bandwidth is exceeded, the network performance may be affected.
+ - If you add multiple listeners to a load balancer, the sum of QPS values of all listeners cannot exceed the QPS defined in each specification.
- The bandwidth is the upper limit of the inbound or the outbound traffic. For example, for small I load balancers, the inbound or outbound traffic cannot exceed 50 Mbit/s.
- The bandwidth included in each specification is the maximum bandwidth provided by ELB. If the maximum bandwidth is exceeded, the network performance may be affected.
|
|---|
|
|---|
|
|---|
