Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- Service Overview
- Billing
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Environment Management
- Application Management
- Component Management
- Instance Management
- Component Configurations
- Component O&M
- System Settings
- Key Operations Recorded by CTS
-
Best Practices
- CAE Best Practices
- Using CAE to Host Nginx Static File Servers
- Interconnecting GitLab with Jenkins for Automatic Build and Deployment on CAE
- Deploying Components Based on the Dependency Sequence Using the Jenkins Pipeline
- Deploying Spring Cloud Applications to CAE to Automatically Connect to the Nacos Engine
- Graceful Startup of a Spring Cloud Application
- Health Check
- Lifecycle Management
- Sending Event Alarms to WeCom
-
Connecting to the CodeArts Pipeline to Automatically Upgrade CAE Components
- Overview
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to a CodeArts Release Repo
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to the OBS Bucket
- Upgrading a CAE Component After Uploading an Image Built Using the Pipeline to the SWR Image Repository
- Configuring PromQL to Implement Custom Auto Scaling
- Configuring the Interconnection Between CAE and DEW to Help Applications Obtain Encrypted Secrets from DEW
- Deploying ASP.NET Core Applications to CAE
- Connecting the Network Through Enterprise Routes
- API Reference
-
FAQs
- Component Management FAQs
- Environment Management
-
Component Configuration FAQs
- Is Manual Scaling Still Effective When a Scaling Policy Is Configured?
- Can Components Be Scaled Without a Scaling Policy?
- Why Is My Instance Abnormal After Cloud Storage Is Configured?
- What Do I Do If a Component Becomes Not Ready?
- How Does CAE Support Dark Launch?
- How Do I Provide Prometheus Metrics for a Java Application?
- System Configuration FAQs
- Service Resources FAQs
- General Reference
Show all
Copied.
Cooperation Between Startup and Liveliness Probes
Prerequisites
- You have created an environment.
- You have created an application.
- You have created and deployed a component. In this example, use the demo-frontend component.
Procedure
- Log in to CAE. Choose Component Configurations.
- Select the target component from the drop-down list in the upper part of the page.
Figure 1 Selecting a component
- Configure the startup and liveliness probes by referring to Figure 2 and Figure 3, and make the configurations take effect. For details, see Configuring Health Check.
The startup probe will check an instance every 5 seconds, starting 10 seconds after instance creation. If the check fails for five consecutive times, the container will be restarted. After the startup probe detects that the instance is healthy, the liveliness probe starts detection to prevent the instance from keeping restarting due to slow program startup.
NOTICE:
Ensure that the program can start within the following period: Latency + Check Interval x Failure Threshold. Otherwise, the startup probe will keep restarting the instance. If you are not sure about the program startup time, increase Failure Threshold and Latency.
As shown in Figure 3, the program needs to start within 35 seconds (10 + 5 x 5 = 35).
- Click Component Events. As shown on the page, the program starts after one startup probe detection failure. Then the liveliness probe is switched to and detects that the instance is healthy.
Figure 4 Viewing eventsFigure 5 Startup probe detection
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot