component life cycle
This article explains the attributes and nouns related to applications, so that you can understand the concept of applications more clearly.
Status of service components
Once the service component is created, it enters the life cycle of the service component. There will be a series of states in the entire life cycle, and each state will be explained below.Most states have a preset timeout period. Regardless of whether the timeout period is exceeded, after 3 minutes , all life cycle operations can be performed on the service component again：：
| state | illustrate |
|---|---|
| under creation | A newly created service component, in the setup phase. |
| under construction | The newly created service component setup is complete, and the first service component version build is in progress.The source code build time-out time is 1 hour, and the Dockerfile build time-out time is 30 minutes.timeout does not mean the build failed, refer to the build log to understand the current progress. |
| scheduling | Once the service component is constructed, it will enter the scheduling state, and the color of theinstance is yellow.In this process, the K8s assigns the host to schedule the instance.If it remains in this state for a long time, it may be because there are no host nodes to run the component. |
| starting | Service component is starting,instance color is yellow.It cannot be accessed temporarily. The startup is divided into two stages, process startup and business startup. If the health check at startup is not configured, as long as the process startup is completed, the startup is considered successful.The startup timeout is 40 seconds * number of instances.startup timeout does not mean startup failed |
| wait to start | The waiting state and the starting state will not appear at the same time. Once the waiting state is entered, the color of theinstance is yellow.Indicates that other service components that the current service component depends on have not been started.You need to wait for the other service components it depends on to start to complete before the current service component enters the starting state. |
| running | All running instances of the service component are in the running state, and the color ofinstances is green.Normally, the running service components can be accessed, or the application may be temporarily unavailable due to slow business startup. |
| abnormal operation | If the number of normal instances of the service component is less than the total instances, it indicates that the application is running abnormally, and the color ofabnormal instances is red.For multi-instance service components, the service components in the abnormal state can provide services as long as there are normal instances.Instance exceptions are mostly due to the abnormal exit of the service component itself or an OOM exit due to insufficient memory.The platform will automatically try to restart the abnormal instance.More application information can be viewed by viewing the service component log, or through command line tools |
| during upgrade | The service component is in the process of rolling update,instance color is yellow.Service components with multiple nodes in their current state can be accessed normally.The upgrade timeout is 3 minutes * number of instances.upgrade timeout does not mean upgrade failure |
| closed | The service component has stopped running, and persistent data still exists.The shutdown timeout is 40 seconds * number of instances.If it is in the state of shutdown and for a long time, and the color of theinstance is black, please contact the operation and maintenance colleagues. |
| unknown | The instance color is light blue, the service component in this state may be due to network blockage, failure to obtain the status of the service component, or abnormal back-end services.You can try to refresh the page. If it cannot be resolved, please contact the operation and maintenance colleagues. |
version of the app
Versions are marked differently for different：of applications0
| App types | Version Information | Example |
|---|---|---|
| Source build | Pull the code from the code repository to build the time stamp of the application | 20180803171811 |
| Docker image | Mirror tag information | 1.15.2-alpine |
| Cloud Market Application | App version | 5.6.7 |