- What's New
- Service Overview
- Getting Started
- User Guide
-
FAQs
- Can I Use the Ping Command to Test Latency?
- How Will I Be Billed for Global Accelerator?
- How Can I Increase the Global Accelerator Quotas?
- How Can I Use Traffic Dial to Distribute Traffic?
- What Types of Endpoints Can Be Added to a Global Accelerator?
- Can I Use Global Accelerator in an Area That Is Not Listed Among the Acceleration Areas?
- What Are the Statuses and Health Check Results of Endpoints?
- What Should I Do If an Endpoint Is Unhealthy?
- Most Frequently Asked Questions
- Configuring the TOA Module
- How Can I Use Global Accelerator to Enable European Users to Access the Applications Deployed in or Outside the Chinese Mainland (Excluding Europe) Faster?
Modifying Health Check Settings
Scenario
You can modify the health check configuration of an endpoint group.
Procedure
- Log in to the Global Accelerator console.
- Search for the global accelerator by name or ID.
- Click the name of the global accelerator to go to the details page.
- Click Endpoint Groups.
- Click the name of the endpoint group whose health check configuration you want to modify.
- In the basic information area, click Configure next to Health Check.
- Configure the parameters. For details, see Table 1.
Table 1 Health check parameters that you can modify Parameter
Description
Health Check
Whether to enable health check.
If you disable health check, requests may be forwarded to unhealthy endpoints.
Protocol
The health check protocol can be TCP.
Default value: TCP.
Port
The port used for health check.
The port number ranges from 1 to 65535.
Advanced Settings
Interval (s)
The maximum time between two consecutive health checks, in seconds.
The interval ranges from 1 to 60.
Timeout (s)
The maximum time required for waiting for a response to a health check request, in seconds.
The timeout ranges from 1 to 60.
Maximum Retries
The maximum number of health check retries allowed.
The value ranges from 1 to 10.
- Click OK.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.