Process fault self-healing method, device and equipment for part in distributed management system

Abstract

The invention discloses a process fault self-healing method, device and equipment for a part in a distributed management system. The method comprises the steps of obtaining configuration information comprising an application program interface address of a distributed management server in the distributed management system and a metadatabase address of a metadatabase in the distributed management system; collecting the current running state of the part from the distributed management server by utilizing the application program interface address; collecting metadata from the metadatabase by utilizing the metadatabase address; according to the current running state and the metadata, performing fault checking on the part; and when it is detected that the faulty part exists, sending a process restart task of the faulty part to the distributed management server by utilizing an application program interface. By utilizing the technical scheme provided by the embodiment of the invention, cross-version compatibility can be realized, the self-healing process is visible, the service integration code is non-invasive, and the process fault self-healing of the part in the distributed management system is simple and efficient.

Description

technical field [0001] The present application relates to the technical field of Internet communication, and in particular to a process failure self-healing method, device and equipment for components in a distributed management system. Background technique [0002] With the rapid development of Internet communication technology, some large-scale Internet business systems will adopt distributed cluster management due to business complexity and other reasons. Subsequently, a large number of service management systems for distributed cluster management have also been produced, such as Apache ambari, etc., but with the gradual increase of nodes in the managed single distributed cluster system, when various component failures caused by hardware and software Some common failures such as insufficient memory, network jitter, disk IO overload, etc. cause the process to terminate. Usually, it only needs to restart the process to achieve self-healing. [0003] The existing fault self...

AI Technical Summary

Problems solved by technology

However, there is a problem of version incompatibility between the above two solutions, and when the component process terminates abnormally, the fault self-healing will silently start the process in the background of the distributed management system to recover, resulting in the fault self-healing process can only be done by logging in to the server Checking the logs of the agent node shows that the self-healing process has a black-box nature; and in the two schemes, in the former scheme, the component configuration file needs to be modified and the process restarted, and in the latter scheme, the self-healing ability of the service failure is disabled by default. Manual operation is required to start each service one by one, and the service integration code needs to be modified to define fault self-healing related information. The operation process is complicated and the maintenance cost of the service integration code is high; therefore, a more reliable or effective solution needs to be provided

Images