Category | Feature |
IP version | IPv4: GWLB supports IPv4 traffic access. |
Listener | Listener protocol and port: Checks for incoming IP packets at a specific IP address using the specified protocol and port. All protocols and ports are supported. Traffic forwarding: Forwards IP traffic.
|
Scheduling algorithm | Five-tuple hash: Distributes a request based on a five-tuple (source IP address, source port, destination IP address, destination port, and IP protocol) hash of the request and ensures that requests with the same hash value are forwarded to the same backend server. Three-tuple hash: Distributes a request based on a three-tuple (source IP address, destination IP address, and IP protocol) hash of the request and ensures that requests with the same hash value are forwarded to the same backend server. Two-tuple hash: Distributes a request based on a two-tuple (source IP address and destination IP address) hash of the request and ensures that requests with the same hash value are forwarded to the same backend server.
|
Reliability | Health check: GWLB performs health checks to determine the availability of backend services. If a backend server is declared unhealthy, GWLB stops forwarding requests to that server and distributes subsequent requests to healthy backend servers. Multi-zone deployment: A GWLB instance can be associated with GWLB endpoints across multiple zones. If the GWLB endpoint in a certain zone fails, the instance can still be accessed through GWLB endpoints in other zones. This ensures business continuity and eliminates single points of failure. Cross-zone forwarding: A GWLB instance deployed in a certain zone can forward traffic to a backend server deployed in another zone, allowing flexible deployment. In addition, a GWLB instance can be associated with backend servers across multiple zones. If the backend server in a certain zone fails, GWLB can stop forwarding requests to that server and distribute subsequent requests to backend servers in other zones.
|
Backend | Server: Supports configuring Elastic Compute Service (ECS) instances, elastic network interfaces (ENIs), and elastic container instances as backend services. IP address: Supports configuring IP addresses as backend services.
|
Advanced feature | Connection draining: After a backend server is removed, existing connections to the server remain open for a specified connection draining timeout. After this timeout, if no new requests are received by the server during the idle connection timeout, the existing connections are closed, and no more packets are forwarded to the server. |
Monitoring and O&M | Instance monitoring: GWLB can integrate with CloudMonitor to offer instance- and zone-based metrics, such as connection, bandwidth, and health check metrics, helping you understand the operational status of your business. |