A primary/secondary server group consists of a primary server and a secondary server. After you select a primary/secondary server group for a listener, requests are forwarded to the primary server when the primary server works as expected. If the primary server fails, requests are forwarded to the secondary server. The time when the system switches to the secondary server is determined by the timeout period set for health checks. Requests are automatically forwarded to the primary server when it recovers.
Prerequisite
- A Classic Load Balancer (CLB) instance is created. For more information, see Create and manage a CLB instance.
- Elastic Compute Service (ECS) instances are created and applications are deployed on the ECS instances to receive requests. For more information, see Create an instance by using the wizard.
Create a primary/secondary server group
Delete a primary/secondary server group
If you no longer use a primary/secondary server group, you can delete the primary/secondary server group. Before you delete a primary/secondary server group, you must disassociate the server group from all listeners.
- Log on to the CLB console.
- In the top navigation bar, select the region where the CLB instance is deployed.
- On the Instances page, click the ID of the CLB instance that you want to manage.
- Click the Primary/Secondary Server Groups tab.
- On the Primary/Secondary Server Groups tab, find the primary/secondary server group that you want to delete and click Delete in the Actions column.
- In the message that appears, click OK.