Host machine container self-healing method, device and system

Abstract

The invention provides a host machine container self-healing method, a device and a system. The host machine container self-healing method comprises the following steps: receiving container restart information from a host machine and container disk information from a monitoring server, wherein both the container restart information and the container disk information comprise container identifiers;judging an exception type according to the container restart information and the container disk information; and repairing the container corresponding to the container identifier according to the abnormal type to complete self-healing. According to the invention, the rapid self-healing capability of the container can be improved, and stable online service is provided for users.

Description

technical field [0001] The present invention relates to the technical field of host machine containers, in particular to a host machine container self-healing method, device and system. Background technique [0002] With the widespread deployment of cloud applications, the scale of management containers is getting larger and larger, and the health and operation monitoring of containers and the ability of self-healing and self-healing are becoming more and more important. At present, resource management on the cloud is mainly managed by the open source management software Kubernetes. Kubernetes provides a container restart self-healing mechanism for unhealthy containers. [0003] In the cluster container management on the cloud, the causes of container exception scenarios are more complicated. Once an exception occurs, the container cannot be repaired immediately, which will affect the online service level of the application, resulting in the unavailability of the application...

AI Technical Summary

Problems solved by technology

[0003] In the cluster container management on the cloud, the causes of container exception scenarios are more complicated. Once an exception occurs, the container cannot be repaired immediately, which will affect the online service level of the application, resulting in the unavailability of the application. Receive and service image

Kubernetes lacks monitoring and self-healing capabilities for sub-healthy scenarios such as the slow response of the container caused by the busy IO of the host itself and the large number of exception logs written in the container, which leads to busy disk IO. Intervening in the self-healing container cannot guarantee the container's ability to provide services online and stably

Images