Distributed cluster management method and device, computer equipment and storage medium

Abstract

The invention relates to a distributed cluster management method and device, computer equipment and a storage medium. The method comprises the following steps: under the condition that a target application in a target node in a distributed cluster is abnormal, obtaining fault analysis information of a target application gateway in the target node, fault analysis information of a target container environment where the target application is deployed and fault analysis information of the target application; if the fault analysis information of the target application represents that the target application has a fault, judging whether the target container environment has a fault according to the fault analysis information of the target container environment, and if the target container environment does not have the fault, sending a fault processing request for the target application to a service grid in the target node; and if the target container environment has a fault, judging whether the target application gateway has a fault according to the fault analysis information of the target application gateway, and if the target application gateway does not have a fault, sending a fault processing request for the target container environment to the target application gateway. By adopting the method, the fault processing efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of distributed technology, and in particular to a distributed cluster management method, apparatus, computer equipment and storage medium. Background Art

[0002] With the development of distributed technology, distributed clusters are being used more and more widely. Active-Active Architecture is a special form of distributed clusters.

[0003] In a multi-active architecture, applications are distributed in multiple computer rooms and provide services to the outside world at the same time. In a multi-active architecture, there may be failures in the nodes of the distributed cluster, so fault handling is required.

[0004] However, current fault handling usually involves redundant design and data backup, etc., and the efficiency of fault handling is low. Summary of the invention

[0005] Based on this, it is necessary to provide a distributed cluster management method, apparatus, computer equipment, computer-readable storage medium and computer program product that can improve management efficiency in response to the above technical problems.

[0006] On the one hand, the present application provides a distributed cluster management method, including: in the event that a target application in a target node in a distributed cluster is abnormal, obtaining fault analysis information of a target application gateway in the target node, fault analysis information of a target container environment in which the target application is deployed, and fault analysis information of the target application; if the fault analysis information of the target application represents a fault of the target application, determining whether the target container environment is faulty based on the fault analysis information of the target container environment, and if the target container environment is not faulty, sending a fault handling request for the target application to a service grid in the target node; if the target container environment is faulty, determining whether the target application gateway is faulty based on the fault analysis information of the target application gateway, and if the target application gateway is not faulty, sending a fault handling request for the target container environment to the target application gateway; if the target application gateway is faulty, sending a fault handling request for the target node to a domain name server.

[0007] On the other hand, the present application also provides a distributed cluster management device, including: an information acquisition module, which is used to obtain the fault analysis information of the target application gateway in the target node, the fault analysis information of the target container environment in which the target application is deployed, and the fault analysis information of the target application when the target application in the target node in the distributed cluster is abnormal; a fault processing module, which is used to determine whether the target container environment is faulty according to the fault analysis information of the target container environment if the fault analysis information of the target application represents the fault of the target application, and if the target container environment is not faulty, send a fault processing request for the target application to the service grid in the target node; the fault processing module is also used to determine whether the target application gateway is faulty according to the fault analysis information of the target application gateway if the target container environment is faulty, and if the target application gateway is not faulty, send a fault processing request for the target container environment to the target application gateway; the fault processing module is also used to send a fault processing request for the target node to the domain name server if the target application gateway is faulty.

[0008] In some embodiments, the device also includes a fault analysis module, which is used to obtain, for each node in the distributed cluster, the gateway status data of the application gateway, the container environment status data of the container environment, and the running status data of the application in the node; for each application, a fault analysis is performed based on the running status data of the application to obtain the fault analysis information of the application; for each container environment, a fault analysis is performed based on the container environment status data of the container environment to obtain the fault analysis information of the container environment; for each application gateway, a fault analysis is performed based on the gateway status data of the application gateway to obtain the fault analysis information of the application gateway.

[0009] In some embodiments, there are multiple running status data of the application, which are the running status data collected for the application in each of multiple consecutive data collection cycles; the fault analysis module is also used to perform fault analysis based on the running status data collected for the application in each of multiple consecutive data collection cycles to obtain fault analysis information of the application.

[0010] In some embodiments, the fault handling request for the target application is used to instruct the service grid to isolate the target application.

[0011] In some embodiments, the fault handling request for the target container environment is used to instruct the target application gateway to isolate the target container environment.

[0012] In some embodiments, the fault handling request for the target node is used to request the domain name server to switch the traffic of the target node to other nodes in the distributed cluster.

[0013] On the other hand, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps in the above-mentioned distributed cluster management method when executing the computer program.

[0014] On the other hand, the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned distributed cluster management method are implemented.

[0015] On the other hand, the present application also provides a computer program product, including a computer program, which implements the steps in the above-mentioned distributed cluster management method when executed by a processor.

[0016] The above-mentioned distributed cluster management method, device, computer equipment, storage medium and computer program product, when the target application in the target node in the distributed cluster is abnormal, obtains the fault analysis information of the target application gateway in the target node, the fault analysis information of the target container environment in which the target application is deployed, and the fault analysis information of the target application. If the fault analysis information of the target application represents the target application fault, then it is determined whether the target container environment is faulty according to the fault analysis information of the target container environment. If the target container environment is not faulty, a fault handling request for the target application is sent to the service grid in the target node. If the target container environment is faulty, then it is determined whether the target application gateway is faulty according to the fault analysis information of the target application gateway. If the target application gateway is not faulty, a fault handling request for the target container environment is sent to the target application gateway. If the target application gateway is faulty, a fault handling request for the target node is sent to the domain name server. For scenarios where applications are deployed in multiple computer rooms or multiple data centers, when an application, container or computer room fails, the present application improves fault handling efficiency through fault handling at different levels. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 An application environment diagram of a distributed cluster management method in one embodiment;

[0019] Figure 2 A schematic diagram of a process flow of a distributed cluster management method in one embodiment;

[0020] Figure 3A schematic diagram of a process for generating fault analysis information in an embodiment;

[0021] Figure 4 A schematic diagram of a scheduling module sending a request according to fault analysis information in an embodiment;

[0022] Figure 5 is a flow chart of a distributed cluster management method in another embodiment;

[0023] Figure 6 is a structural block diagram of a distributed cluster management device in one embodiment;

[0024] Figure 7 is an internal structure diagram of a computer device in one embodiment;

[0025] Figure 8 FIG. 4 is a diagram showing the internal structure of a computer device in another embodiment. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0027] The distributed cluster management method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown, the application environment includes a management device, a domain name server, and multiple nodes in a distributed cluster. Only two nodes are drawn in the figure, namely node 1 and node 2. The application does not limit the number of nodes. The domain name server can be an ordinary domain name server or an intelligent domain name server, namely an intelligent DNS (Domain Name System) server. The management device can be a server or a terminal. Different nodes can be located in different computer rooms, for example, node 1 is located in computer room 1, and node 2 is located in computer room 2. Each node includes an application gateway, a service grid, and a container environment. There can be one or more container environments in each node, and multiple refers to at least two. For example, in the figure, there are container environments 1 and 2 in node 1, and container environments 3 and 4 in node 2. Each container environment includes at least one application container. As shown in the figure, container environments 1 to 4 respectively include 2 application containers. An application container is a lightweight, independent running instance that encapsulates an application and its running environment. A container environment refers to the sum of infrastructure and configurations that support container operation. The container environment provides the necessary resources and services for the container to ensure that the container can run normally and efficiently. A container refers to a lightweight, independent, executable software package. An application container is a specific form of container that focuses on providing an operating environment for applications. The applications running in different application containers can be the same or different. For example, the application containers in each node run the same application, and the applications running in the application container can be micro-applications.

[0028] Figure 1The system in the paper is based on cloud native technologies such as microservices and containers. The running status data of the application is separated from the service, so that the service itself no longer stores any information related to the user session. Any request can be processed by any application instance. Then, the application is horizontally expanded and deployed to multiple container environments. At the same time, multiple container environments are deployed in two different computer rooms (computer room 1 and computer room 2). These two computer rooms are independent fault isolation domains, which have met the multi-active deployment requirements. The management device realizes the multi-active switching capability of the system under different fault scenarios. Specifically, by monitoring and analyzing the running status of the application, the running status of the container environment, and the running status of the application gateway, when the application, container environment or application gateway fails, the traffic is switched. The relevant modules of the management device are as follows: Monitoring module: regularly monitors the health status of the application, container environment, and data center, and sends it to the data analysis module. Analysis module: analyzes the monitoring data, comprehensively judges the health status of the application, container environment or computer room, and sends the analysis results to the scheduling module. Scheduling module: receives the analysis and judgment results, and notifies the relevant modules to perform fault switching according to different levels of faults. The switching mechanism is as follows: a) Micro application failure: notify the service grid to isolate the faulty application node and implement traffic switching. b) Container environment level: notify the application gateway to isolate the faulty container environment and switch traffic. c) Computer room level (data center level): notify the intelligent DNS service to switch the domain name and switch traffic. Among them, Multi-Active: the information system uses two or more information systems deployed in multiple geographical nodes to work together to achieve the ability of parallel multi-point access to services, parallel multi-point processing of services, and parallel multi-point storage of data. When a disaster or failure occurs in the information system of some geographical nodes, only part of the business is affected, and the information system deployed in other geographical nodes can complete the business takeover in time.

[0029] Specifically, when the target application in the target node in the distributed cluster is abnormal, the management device obtains the fault analysis information of the target application gateway in the target node, the fault analysis information of the target container environment in which the target application is deployed, and the fault analysis information of the target application. If the fault analysis information of the target application represents the fault of the target application, the management device determines whether the target container environment is faulty according to the fault analysis information of the target container environment. If the target container environment is not faulty, the management device sends a fault processing request for the target application to the service grid in the target node; if the target container environment is faulty, the management device determines whether the target application gateway is faulty according to the fault analysis information of the target application gateway. If the target application gateway is not faulty, the management device sends a fault processing request for the target container environment to the target application gateway; if the target application gateway is faulty, the management device sends a fault processing request for the target node to the domain name server. Among them, the fault analysis information can be obtained by the analysis module. The monitoring module is used to obtain the gateway status data of the application gateway in each node, the container environment status data of the container environment, and the running status data of the application, and transmit the obtained data to the analysis module. The analysis module analyzes the acquired data to obtain the fault analysis information, and writes the fault analysis information into the fault analysis database. The application is deployed in multiple computer rooms or multiple data centers. When a failure occurs in the application, container, or computer room, this application implements multi-active capabilities of the application and ensures business continuity through fault diagnosis and switching at different levels.

[0030] Among them, the terminal can be but not limited to various personal computers, laptops, smart phones, tablets, etc. The server can be implemented as an independent server or a server cluster composed of multiple servers, or it can be a cloud server. The cloud server is used to provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data and artificial intelligence platforms. The management node, domain name server and service node can be directly or indirectly connected through wired or wireless communication, and this application does not limit this.

[0031] In some embodiments, Figure 2 As shown, a distributed cluster management method is provided, which can be executed by a terminal or a server, or by a terminal and a server together. Figure 1 The management device in FIG. 1 is taken as an example to illustrate, including the following steps 202 to 208. Among them:

[0032] Step 202, when the target application in the target node in the distributed cluster is abnormal, obtain fault analysis information of the target application gateway in the target node, fault analysis information of the target container environment where the target application is deployed, and fault analysis information of the target application.

[0033] The application is an application running in the above-mentioned application container. The fault analysis information is used to characterize whether a fault exists. The target container environment belongs to the target node.

[0034] Specifically, the management device can periodically obtain the running status data of the application and determine whether the application is abnormal based on the application status data. The abnormality of the application is not necessarily caused by the failure of the application itself, but may also be caused by the failure of the container environment or the application gateway. The running status data may include a status code, and whether the application is abnormal can be determined based on the status code.

[0035] Step 204: If the fault analysis information of the target application indicates a target application fault, determine whether the target container environment is faulty based on the fault analysis information of the target container environment; if the target container environment is not faulty, send a fault handling request for the target application to the service grid in the target node.

[0036] The fault analysis information of the target container environment is used to indicate whether the target container environment is faulty.

[0037] A fault handling request for the target application, used to request the service grid to isolate the target application.

[0038] Step 206: If the target container environment fails, determine whether the target application gateway fails based on the fault analysis information of the target application gateway; if the target application gateway does not fail, send a fault handling request for the target container environment to the target application gateway.

[0039] The fault analysis information of the target application gateway is used to indicate whether the target application gateway is faulty. The fault handling request for the target container environment is used to request the target application gateway to isolate the target container environment.

[0040] Step 208: If the target application gateway fails, a fault handling request for the target node is sent to the domain name server.

[0041] The fault handling request of the target node is used to request the domain name service to distribute the traffic allocated to the target node to other nodes in the distributed cluster.

[0042] In the above-mentioned distributed cluster management method, when the target application in the target node in the distributed cluster is abnormal, the fault analysis information of the target application gateway in the target node, the fault analysis information of the target container environment in which the target application is deployed, and the fault analysis information of the target application are obtained. If the fault analysis information of the target application represents the target application fault, then it is determined whether the target container environment is faulty according to the fault analysis information of the target container environment. If the target container environment is not faulty, a fault handling request for the target application is sent to the service grid in the target node. If the target container environment is faulty, then it is determined whether the target application gateway is faulty according to the fault analysis information of the target application gateway. If the target application gateway is not faulty, a fault handling request for the target container environment is sent to the target application gateway. If the target application gateway is faulty, a fault handling request for the target node is sent to the domain name server. For scenarios where applications are deployed in multiple computer rooms or multiple data centers, when an application, container, or computer room fails, this application improves fault handling efficiency through fault handling at different levels. For scenarios where applications are deployed in multiple computer rooms or multiple data centers, when an application, container, or computer room fails, this application implements multi-active capabilities of the application and ensures the robustness of the distributed cluster by performing fault judgment and switching at different levels.

[0043] In some embodiments, the method also includes: for each node in the distributed cluster, obtaining the gateway status data of the application gateway, the container environment status data of the container environment, and the running status data of the application in the node; for each application, performing a fault analysis based on the running status data of the application to obtain fault analysis information of the application; for each container environment, performing a fault analysis based on the container environment status data of the container environment to obtain fault analysis information of the container environment; for each application gateway, performing a fault analysis based on the gateway status data of the application gateway to obtain fault analysis information of the application gateway.

[0044] The application running status data includes but is not limited to at least one of the average response time (also referred to as the average response duration), the status code or the error rate. The status code can be used to determine whether the application running in the application container is abnormal, that is, whether it can be accessed normally. For example, if the status code is 200, it means that the application can be accessed normally. If the status code is other than 200, such as 4XX or 5XX, it means that the application cannot be accessed normally.

[0045] The container environment status data includes but is not limited to at least one of the container status or the health status. The container status is divided into a running state and a non-running state, and the health status is divided into a healthy state and an unhealthy state.

[0046] The gateway status data includes but is not limited to at least one of average response duration (ie, average response time), response code distribution data, CPU usage, memory usage, input traffic, output traffic, or error rate.

[0047] In some embodiments, for the application container, the management device can analyze the error rate and the average response time to obtain the fault analysis information of the application container. Specifically, when at least one of the error rate is greater than the error rate threshold and the average response time is greater than the time threshold, it is determined that the application gateway has failed. The error rate threshold and the time threshold can be set as needed, for example, the error rate threshold can be 80%, and the time threshold can be 5 seconds.

[0048] In some embodiments, for the container environment, the management node can analyze the container state or health state to obtain fault analysis information of the container environment. Specifically, when at least one of the container state is a non-operating state and the health state is an unhealthy state, it is determined that the container environment has a fault.

[0049] In some embodiments, for the application gateway, the management device can analyze the error rate or average response time of the application gateway to obtain fault analysis information of the application gateway. Specifically, when at least one of the error rate is greater than the error rate threshold and the average response time is greater than the time threshold, it is determined that the application gateway has failed. The error rate threshold and the time threshold can be set as needed, for example, the error rate threshold can be 80%, and the time threshold can be 5 seconds.

[0050] In some embodiments, the management device may write each fault analysis information into a fault analysis database. The management device may periodically execute the process of generating fault analysis information.

[0051] In this embodiment, fault analysis is performed on the application grid, container environment, and application in each node in the distributed cluster to generate corresponding fault analysis information, which helps to detect the distributed cluster globally and improve detection efficiency.

[0052] In some embodiments, there are multiple running status data of the application, which are the running status data obtained by collecting the application in each data collection cycle in multiple consecutive data collection cycles; fault analysis is performed based on the running status data of the application to obtain fault analysis information of the application, including: fault analysis is performed based on the running status data obtained by collecting the application in each data collection cycle in multiple consecutive data collection cycles to obtain fault analysis information of the application.

[0053] Specifically, the multiple consecutive data sampling periods may be, for example, three consecutive data sampling periods. One data sampling period may be determined according to actual needs. For example, one data sampling period may be 1 minute.

[0054] In some embodiments, the management device performs fault analysis on the data obtained in each data sampling period in multiple data sampling periods. If the analysis results corresponding to the data obtained in each data sampling period all indicate that a fault exists, the fault analysis information is determined to be information indicating that a fault exists.

[0055] In some embodiments, fault analysis is performed on container environment status data collected from the container environment in each of a plurality of consecutive data collection cycles to obtain fault analysis information of the container environment.

[0056] In some embodiments, fault analysis is performed on the gateway status data collected from the application gateway in each data collection cycle in a plurality of consecutive data collection cycles to obtain fault analysis information of the application gateway.

[0057] In some embodiments, Figure 3 As shown, a flow chart of generating fault analysis information and writing it into a fault analysis database is shown.

[0058] In this embodiment, the accuracy of the fault analysis information can be improved by performing fault analysis on data from a plurality of consecutive data sampling cycles.

[0059] In some embodiments, the fault handling request for the target application is used to instruct the service grid to isolate the target application.

[0060] In this embodiment, by isolating the target application, traffic can be directed to normal applications, so that the application can provide services normally to the outside world, thereby improving the robustness of the distributed cluster.

[0061] In some embodiments, the fault handling request for the target container environment is used to instruct the target application gateway to isolate the target container environment.

[0062] In this embodiment, by isolating the target container environment, traffic can be directed to a normal container environment, so that the application can provide services normally to the outside world, thereby improving the robustness of the distributed cluster.

[0063] In some embodiments, the fault handling request for the target node is used to request the domain name server to switch the traffic of the target node to other nodes in the distributed cluster.

[0064] Among them, other nodes can be any normal nodes in the distributed cluster.

[0065] In this embodiment, traffic can be switched to normal nodes, so that applications in normal nodes can provide normal services to the outside world, thereby improving the robustness of the distributed cluster.

[0066] In some embodiments, the scheduling module in the management device can obtain fault analysis information from the fault analysis database and send a corresponding fault processing request according to the fault analysis information. Figure 4 In the process, the scheduling module reads the fault analysis information from the fault analysis database and sends a notification, i.e., the corresponding fault handling request, to the service grid, application gateway, or smart DNS, i.e., domain name server. Figure 5 As shown, a flow chart of a distributed cluster management method is shown.

[0067] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0068] Based on the same inventive concept, the embodiment of the present application also provides a distributed cluster management device for implementing the above-mentioned distributed cluster management method. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above-mentioned method, so the specific limitations in one or more distributed cluster management device embodiments provided below can refer to the above-mentioned limitations on the distributed cluster management method, and will not be repeated here.

[0069] In some embodiments, Figure 6 As shown, a distributed cluster management device is provided, including: an information acquisition module 602 and a fault processing module 604, wherein:

[0070] The information acquisition module 602 is used to acquire the fault analysis information of the target application gateway in the target node, the fault analysis information of the target container environment where the target application is deployed, and the fault analysis information of the target application when the target application in the target node in the distributed cluster is abnormal.

[0071] The fault processing module 604 is used to determine whether the target container environment is faulty according to the fault analysis information of the target container environment if the fault analysis information of the target application indicates a target application fault; if the target container environment is not faulty, send a fault processing request for the target application to the service grid in the target node.

[0072] The fault handling module 604 is also used to determine whether the target application gateway is faulty according to the fault analysis information of the target application gateway if the target container environment fails, and if the target application gateway is not faulty, send a fault handling request for the target container environment to the target application gateway.

[0073] The fault handling module 604 is further configured to send a fault handling request for the target node to the domain name server if the target application gateway fails.

[0074] In some embodiments, the device also includes a fault analysis module, which is used to obtain, for each node in the distributed cluster, the gateway status data of the application gateway, the container environment status data of the container environment, and the running status data of the application in the node; for each application, a fault analysis is performed based on the running status data of the application to obtain the fault analysis information of the application; for each container environment, a fault analysis is performed based on the container environment status data of the container environment to obtain the fault analysis information of the container environment; for each application gateway, a fault analysis is performed based on the gateway status data of the application gateway to obtain the fault analysis information of the application gateway.

[0075] In some embodiments, there are multiple running status data of the application, which are the running status data collected for the application in each of multiple consecutive data collection cycles; the fault analysis module is also used to perform fault analysis based on the running status data collected for the application in each of multiple consecutive data collection cycles to obtain fault analysis information of the application.

[0076] In some embodiments, the fault handling request for the target application is used to instruct the service grid to isolate the target application.

[0077] In some embodiments, the fault handling request for the target container environment is used to instruct the target application gateway to isolate the target container environment.

[0078] In some embodiments, the fault handling request for the target node is used to request the domain name server to switch the traffic of the target node to other nodes in the distributed cluster.

[0079] Each module in the above-mentioned distributed cluster management device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0080] In some embodiments, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 7As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data involved in the distributed cluster management method. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a distributed cluster management method is implemented.

[0081] In some embodiments, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a distributed cluster management method is realized. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0082] Those skilled in the art will understand that Figure 7 and Figure 8The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0083] In some embodiments, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned distributed cluster management method when executing the computer program.

[0084] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned distributed cluster management method are implemented.

[0085] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above-mentioned distributed cluster management method when executed by a processor.

[0086] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0087] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0088] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0089] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A distributed cluster management method, characterized in that: The method comprises: In the case where a target application in a target node in a distributed cluster is abnormal, obtaining fault analysis information of a target application gateway in the target node, fault analysis information of a target container environment in which the target application is deployed, and fault analysis information of the target application; If the fault analysis information of the target application indicates that the target application has a fault, determining whether the target container environment has a fault according to the fault analysis information of the target container environment; if the target container environment has not a fault, sending a fault handling request for the target application to the service grid in the target node; If the target container environment fails, determining whether the target application gateway fails according to the fault analysis information of the target application gateway; if the target application gateway does not fail, sending a fault handling request for the target container environment to the target application gateway; If the target application gateway fails, a fault handling request for the target node is sent to the domain name server.

2. The method according to claim 1, characterized in that The method further comprises: For each node in the distributed cluster, obtain the gateway status data of the application gateway in the node, the container environment status data of the container environment, and the running status data of the application; For each application, performing a fault analysis according to the running status data of the application to obtain fault analysis information of the application; For each of the container environments, performing a fault analysis according to the container environment status data of the container environment to obtain fault analysis information of the container environment; For each of the application gateways, a fault analysis is performed according to the gateway status data of the application gateway to obtain fault analysis information of the application gateway.

3. The method according to claim 2, characterized in that The running status data of the application is multiple, which are the running status data collected from the application in each data collection cycle in multiple consecutive data collection cycles; The performing fault analysis according to the running status data of the application to obtain fault analysis information of the application includes: Fault analysis is performed on the operating status data obtained by collecting the application in each data collection cycle in a plurality of consecutive data collection cycles to obtain fault analysis information of the application.

4. The method according to any one of claims 1 to 3, characterized in that: A fault handling request for the target application, used to instruct the service grid to isolate the target application.

5. The method according to any one of claims 1 to 3, characterized in that: The fault handling request for the target container environment is used to instruct the target application gateway to isolate the target container environment.

6. The method according to any one of claims 1 to 3, characterized in that: The fault handling request for the target node is used to request the domain name server to switch the traffic of the target node to other nodes in the distributed cluster.

7. A distributed cluster management device, characterized in that: The device comprises: An information acquisition module, used to acquire, when a target application in a target node in a distributed cluster is abnormal, fault analysis information of a target application gateway in the target node, fault analysis information of a target container environment in which the target application is deployed, and fault analysis information of the target application; a fault processing module, configured to, if the fault analysis information of the target application indicates that the target application has failed, determine whether the target container environment has failed according to the fault analysis information of the target container environment, and if the target container environment has not failed, send a fault processing request for the target application to the service grid in the target node; The fault processing module is further configured to determine whether the target application gateway is faulty according to the fault analysis information of the target application gateway if the target container environment is faulty, and send a fault processing request for the target container environment to the target application gateway if the target application gateway is not faulty; The fault processing module is further configured to send a fault processing request for the target node to the domain name server if the target application gateway fails.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images