Manage origin pools

Overview

An origin pool provides weighted origin fetch scheduling across multiple origin servers. It can be referenced by ESA domain names and TCP/UDP proxy applications. By combining origin pools with load balancing, you can configure multiple policies to enhance service availability.

Create an origin pool

1. In the ESA console, select Websites, and in the Website column, click the target site.

2. In the left navigation pane, choose Traffic > Origin Pools.

3. On the Origin Pools page, click Create Origin Pool.

4. On the Create Origin Pool page, enter a Pool Name and add at least one Origin Server.

   Parameter	Description
   Pool Name	The name of the origin pool, which cannot be changed after the pool is created. The name can be up to 200 characters long and can contain only the following characters: Lowercase letters (a-z) Digits Hyphens (-), but not at the beginning or end
   Domain Name	Automatically generated by the system. The format is: [pool name].origin-pool.[your website domain name].
   Origin Server-Name	A custom name for the origin server.
   Origin Server-Type	Select the type of your origin server: IP/Domain: An IPv4 address, IPv6 address, or domain name. OSS: Alibaba Cloud Object Storage Service (OSS). S3-compatible: S3-compatible storage. EAG Origin-fetch Acceleration: Edge Acceleration Gateway (EAG) origin acceleration service. Select an EAG domain name from the drop-down list. After you select a domain name, the system displays the associated EAG instances, including the region, IP address, running status, and instance ID.
   Origin Server-Origin Address	The address of your origin server.
   Origin Server-Weight and Percent	The weight determines the traffic distribution. The default is 50, and the value can range from 0 to 100, with a minimum increment of 1. If you set the weight to 0, no origin fetch requests are sent to this origin server. Percentage: The system automatically calculates a percentage value based on the configured weight, which indicates the traffic distribution ratio.
   Origin Server-Origin Host Header	Specifies the Host header that ESA uses for origin fetch requests to this origin server. Note If you leave this field blank, ESA uses the host policy from your DNS settings.
   Origin Server-Origin Fetch IP Version	Specifies the policy that ESA POPs use to select an IP version (IPv4 or IPv6) for origin fetch requests. The default policy is Random Poll IPv4/IPv6 Origin. Random Poll IPv4/IPv6 Origin: ESA randomly selects an IP address from all available IPv4 and IPv6 addresses of the origin servers. Use case: Your origin server supports both IPv4 and IPv6, and you want to balance the load between them. Benefit: Fully utilizes dual-stack capabilities and prevents overloading a single protocol. Prioritize IPv4 Origin: ESA connects using IPv4 addresses. If all IPv4 connections fail, it falls back to IPv6. Use case: Your IPv4 network is more stable or has broader coverage, or your origin server's IPv6 support is incomplete. Benefit: Maximizes compatibility with traditional deployment environments. Prioritize IPv6 Origin: ESA connects using IPv6 addresses. If all IPv6 connections fail, it falls back to IPv4. Use case: Your origin server fully supports IPv6, and you want to increase the proportion of IPv6 traffic, for example, to comply with IPv6 adoption initiatives. Benefit: Increases IPv6 traffic to your origin server. Prioritize Client IP Version: ESA prioritizes using the same IP protocol version (IPv4 or IPv6) for origin fetch as the one that the client uses to access an ESA node. If a client connects using IPv6, ESA prioritizes IPv6 for the origin fetch. If a client connects using IPv4, ESA prioritizes IPv4 for the origin fetch. Use case: You want to maintain end-to-end protocol consistency for easier debugging or to meet specific security or auditing requirements. Benefit: Simplifies traffic path tracing and ensures a more consistent experience if the origin server has a robust dual-stack implementation.

5. Click OK to create the origin pool.

Delete an origin pool

1. In the ESA console, select Websites, and in the Website column, click the target site.

2. In the left navigation pane, choose Traffic > Origin Pools.

3. Find the origin pool you want to delete and click Delete.

   Note

   If a load balancer references the origin pool, you must first remove the pool from the load balancer's configuration. Deleting a referenced origin pool can cause traffic routing errors, service interruptions, and health check failures. For instructions, see Delete an origin pool referenced by a load balancer.

Feature availability