Instance invalid self-healing identification method and device, electronic equipment and storage medium
By judging and verifying the operating status of the instance, the system oscillation problem caused by unknown reasons caused by the instance's self-healing is solved, and the system stability is improved.
Patent Information
- Application Number
- CN202411116315.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-14
- Publication Date
- 2024-12-10
AI Technical Summary
In the prior art, the root cause of the example triggering self-healing may not be caused by the example itself, which leads to repeated self-healing of the example, causing system oscillation, and causing system self-healing collapse.
By judging the operating status of the target instance, determine whether it is necessary to perform a self-healing operation and verify it after self-healing. If self-healing is found to be invalid, exit the self-healing operation to avoid the occurrence of invalid self-healing. Specific steps include: judge example abnormalities based on key indicators such as number of threads, garbage collection information, memory usage, etc., obtain log data to judge the status of manual intervention, compare the similarity of monitoring indicators to determine the status changes, and exit self-healing if it is invalid.
It avoids the occurrence of invalid self-healing, improves the stability of system operation, prevents the system from collapse caused by repeated self-healing, and ensures the effectiveness of self-healing operations.
Smart Images
Figure CN119105893A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a method, device, electronic device and storage medium for identifying invalid self-healing of an instance. Background Art
[0002] Instance self-healing means that a virtual machine or container instance automatically triggers a preset restart method under a specific monitoring state to restore the instance to normal working state.
[0003] The root cause of the instance triggering self-healing may not be caused by the instance itself. When the instance is restarted according to the self-healing script, the system problem is not solved. At this time, the self-healing condition is often triggered again, resulting in repeated self-healing of the instance, causing system shock, resulting in self-healing crash of the system, and aggravating the impact of the system failure. Summary of the invention
[0004] The present invention provides a method, device, electronic device and storage medium for identifying invalid self-healing of an instance, so as to solve the technical problem in the prior art that the root cause of the instance triggering self-healing may not be caused by the instance itself, resulting in repeated self-healing of the instance, causing system oscillation and causing self-healing crash of the system.
[0005] The present invention provides a method for identifying ineffective self-healing, comprising the following steps: Determine the running status of the target instance and determine whether the target instance needs to perform a self-healing operation; After the target instance performs a self-healing operation, performing a self-healing check on the target instance, and if it is determined that the self-healing of the target instance is invalid, exiting the self-healing operation of the target instance; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
[0006] According to a method for identifying invalid instance self-healing provided by the present invention, judging the running state of a target instance and determining that the target instance needs to perform a self-healing operation includes: Based on the key indicators of the target instance that trigger instance self-healing, determine that the operating indicators of the target instance are abnormal, where the key indicators include one or more of the number of threads of the target instance, garbage collection information of the target instance, memory usage of the target instance, and database connection information of the target instance; Detecting the connectivity of the target instance and the service availability of the target instance to determine that the target instance is operating abnormally; Based on the abnormality of the operating indicator of the target instance and the abnormal operation of the target instance, it is determined that the target instance needs to perform a self-healing operation.
[0007] According to a method for identifying invalid self-healing of an instance provided by the present invention, the step of determining that the target instance is in a state of manual intervention includes: Obtaining log data of the target instance within a preset time period; The log data is analyzed, and when it is determined that the log data contains remote login protocol information or the log data contains remote access protocol information, it is determined that the target instance is in a manual intervention state.
[0008] According to a method for identifying invalid instance self-healing provided by the present invention, determining that the running state of the target instance has not changed before and after the self-healing includes: Obtaining a first monitoring indicator before the target instance is self-healed and a second monitoring indicator after the target instance is self-healed; The first monitoring indicator is compared with the second monitoring indicator to determine that the running state of the target instance has not changed.
[0009] According to a method for identifying invalid self-healing of an instance provided by the present invention, comparing the first monitoring indicator with the second monitoring indicator to determine that the running state of the target instance has not changed includes: Determine the similarity between the first monitoring indicator and the second monitoring indicator based on the Mahalanobis distance; When the similarity is less than a preset similarity threshold, it is determined that the running state of the target instance has not changed.
[0010] According to an example of an ineffective self-healing identification method provided by the present invention, the method further includes: After the target instance performs a self-healing operation, a self-healing check is performed on the target instance. If it is determined that the self-healing of the target instance is not invalid self-healing, the self-healing operation of the target instance is repeatedly performed.
[0011] The present invention also provides an identification device for invalid self-healing of an instance, comprising the following modules: A judgment module, used to judge the running state of the target instance and determine whether the target instance needs to perform a self-healing operation; A verification module, configured to perform a self-healing verification on the target instance after the target instance performs a self-healing operation, and to exit the self-healing operation of the target instance if it is determined that the self-healing of the target instance is invalid; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
[0012] The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method for identifying invalid self-healing as described in any of the above-mentioned examples is implemented.
[0013] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for identifying invalid self-healing as described in any of the above-mentioned examples.
[0014] The present invention also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method for identifying invalid self-healing as described in any of the above examples is implemented.
[0015] The method, device, electronic device and storage medium for identifying invalid self-healing of an instance provided by the present invention review the self-healing request to determine whether the current self-healing conflicts with human operation, and also determine whether the current self-healing can solve the problem of the current instance, thereby avoiding the occurrence of invalid self-healing and avoiding the possibility that the fundamental reason for the instance triggering self-healing is not caused by the instance itself, resulting in repeated self-healing of the instance, causing system shock, and causing the serious consequence of self-healing collapse of the system, thereby improving the stability of system operation. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0017] Figure 1 It is a flow chart of the method for identifying invalid self-healing provided by the present invention.
[0018] Figure 2 The present invention is a schematic diagram of the structure of a device for applying the method for identifying invalid self-healing provided by the present invention.
[0019] Figure 3 It is a schematic diagram of the instance controlled determination flow provided by the present invention.
[0020] Figure 4 It is a schematic diagram of the state verification process before and after self-healing of an example provided by the present invention.
[0021] Figure 5It is a schematic diagram of the structure of an example invalid self-healing identification device provided by the present invention.
[0022] Figure 6 It is a structural schematic diagram of the electronic device provided by the present invention. DETAILED DESCRIPTION
[0023] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0024] Self-healing is a means of automatically recovering abnormal instances to prevent services from being affected due to system anomalies, request backlogs, instance downtime, or no response. The complete self-healing process usually consists of three parts: monitor, discriminator, and executor. The monitor is responsible for collecting one or more operating data indicators of the business instance in real time; the discriminator calculates the indicators, estimates single-dimensional or multi-dimensional baseline rules, and determines whether the business instance is in an abnormal state; the executor is responsible for intervening in abnormal instances and using preset automated operation scripts to restart, rebuild, and other recovery operations on the instances. The use of self-healing can effectively improve the overall stability and availability of the business system and liberate operation and maintenance capabilities.
[0025] In some scenarios, the root cause of the instance triggering self-healing is not caused by the instance itself. When the instance is restarted according to the self-healing script, the system problem is not solved. At this time, the self-healing condition is often triggered again, causing the instance to self-heal repeatedly, causing system shock, causing the system to self-heal and crash, and aggravating the impact of the system failure.
[0026] For the above scenario, the relevant method is generally to set a cooling time in the self-healing script to prevent the newly restarted instance from self-healing again, thereby preventing the instance from being in the restart process and unable to provide services. However, this method can only alleviate the occurrence of repeated self-healing. Once the cooling time expires, the instance will be automatically self-healed again. In addition, if the judgment condition is too harsh, the real same anomaly cannot be identified; if the judgment condition is too broad, normal alarms may be blocked.
[0027] In addition, when an instance is published, changed, or modified manually, the system monitoring indicators may temporarily touch the preset red line, thereby triggering unnecessary self-healing and interfering with the publishing operation.
[0028] For scenarios with manual operation, the relevant method is to set a switch for the self-healing script and control it uniformly. Before manual operation, the self-healing script needs to be manually turned off before the construction operation is carried out; after the construction is completed, the self-healing script needs to be turned on again. However, the solution has a low degree of automation, there is a possibility of missing operations, and the system control is difficult.
[0029] In view of the defects of the related methods, the present invention provides a method for identifying invalid self-healing of an instance. Figure 1 is a flow chart of the method for identifying invalid self-healing provided by the present invention, such as Figure 1 As shown, the method includes the following: Step 110: determine the running status of the target instance and determine whether the target instance needs to perform a self-healing operation.
[0030] Step 120, after the target instance performs a self-healing operation, perform a self-healing check on the target instance, and if it is determined that the self-healing of the target instance is invalid, exit the self-healing operation of the target instance; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
[0031] The execution subject of the invalid self-healing identification method provided by the present invention can be an electronic device, a component in an electronic device, an integrated circuit, or a chip. The electronic device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc., and the non-mobile electronic device can be a server, a network attached storage (NAS), or a personal computer (PC), etc., which is not specifically limited by the present invention.
[0032] The following takes the method for identifying invalid self-healing provided by the present invention executed by a computer as an example to describe the technical solution of the present invention in detail.
[0033] In step 110, the running state of the target instance is judged to determine whether the target instance needs to perform a self-healing operation.
[0034] Observe the health of the target instance itself as the key indicator to trigger instance self-healing. Collect indicators such as the number of threads, garbage collection (GC), memory usage, and database connection status of the instance.
[0035] After collecting the indicators, a judgment is made based on the collected indicators to determine whether the target instance is running normally, thereby determining the running status of the target instance.
[0036] The running status of the target instance can be further judged based on periodic detection of the instance's connectivity and service availability as one of the auxiliary indicators of instance abnormality, to prevent the situation where the instance's own performance is normal but self-healing is not triggered due to external service abnormalities.
[0037] In step 120, after the target instance performs a self-healing operation, a self-healing check is performed on the target instance, and if it is determined that the self-healing of the target instance is invalid, the self-healing operation of the target instance is exited; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
[0038] When it is determined that the target instance needs to perform a self-healing operation, a self-healing operation is performed on the target instance.
[0039] After the target instance performs a self-healing operation, a self-healing check is performed on the target instance and the self-healing request is reviewed to prevent unexpected self-healing from occurring.
[0040] Determine whether the instance is in a state of manual intervention to prevent the instance from being mistakenly self-healed during manual intervention; at the same time, after a self-healing, compare the monitoring indicators before and after the instance self-healing to determine whether the previous self-healing was effective. If the previous self-healing did not change the running status of the instance, the subsequent self-healing requests of the instance are prohibited to prevent the instance from entering a state of cyclic self-healing.
[0041] The method for identifying invalid self-healing of an instance provided by the present invention reviews the self-healing request to determine whether the current self-healing conflicts with human operation, and also determines whether the current self-healing can solve the problem of the current instance, thereby avoiding the occurrence of invalid self-healing and avoiding the possibility that the fundamental reason for the instance triggering self-healing is not caused by the instance itself, resulting in repeated self-healing of the instance, causing system shock, and causing the serious consequence of self-healing collapse of the system, thereby improving the stability of system operation.
[0042] In one embodiment, judging the running status of the target instance and determining that the target instance needs to perform a self-healing operation includes: determining that the running indicators of the target instance are abnormal based on key indicators that trigger instance self-healing in the target instance, the key indicators including one or more of the number of threads of the target instance, garbage collection information of the target instance, memory usage of the target instance, and database connection information of the target instance; detecting the connectivity of the target instance and the service availability of the target instance to determine that the target instance is running abnormally; determining that the target instance needs to perform a self-healing operation based on the abnormal running indicators of the target instance and the abnormal running of the target instance.
[0043] Observe the health of the target instance itself as the key indicator to trigger instance self-healing. Collect indicators such as the number of threads, garbage collection (GC) information, memory usage, and database connection status of the instance.
[0044] After collecting the indicators, a judgment is made based on the collected indicators to determine whether the operating indicators of the target instance are abnormal.
[0045] The judgment on the running state of the target instance may be further based on periodically detecting the connectivity and service availability of the instance to determine that the target instance is running abnormally.
[0046] Based on the abnormal operation indicators of the target instance and the abnormal operation of the target instance, the operation status of the target instance is judged, and it is determined that the target instance needs to perform a self-healing operation.
[0047] In one embodiment, determining that the target instance is in a manual intervention state includes: obtaining log data of the target instance within a preset time period; analyzing the log data, and determining that the target instance is in a manual intervention state when the log data contains remote login protocol information or the log data contains remote access protocol information.
[0048] Determining that the target instance is in a state of manual intervention is a verification of the instance's controlled state. The purpose is to determine whether the instance is currently under a manual command. In this case, even if the instance is determined to be abnormal by the anomaly detector, it should not be self-healed to avoid interrupting the normal operation process.
[0049] Whether it is manually logging into the instance remotely, or further managing the virtual machine through the control node, or managing the container cluster through the cloud platform, the underlying implementation method is basically the remote login protocol SSH or the remote access protocol Telnet. Therefore, the controlled state of the instance is determined by monitoring the login and operation logs of the instance. When a self-healing request is monitored, it actively obtains the acct, sudolog, lastlog, utmp and other log data of the instance within the preset time period. Based on the log data indicating that the instance has been issued instructions within a certain period of time, it is determined that the current instance host is in a controlled state, and it can be determined that the target instance is in a state of manual intervention.
[0050] In one embodiment, determining that the operating status of the target instance has not changed before and after self-healing includes: obtaining a first monitoring indicator of the target instance before self-healing and a second monitoring indicator of the target instance after self-healing; comparing the first monitoring indicator with the second monitoring indicator to determine that the operating status of the target instance has not changed.
[0051] Comparing the first monitoring indicator with the second monitoring indicator to determine that the running state of the target instance has not changed includes: Determine the similarity between the first monitoring indicator and the second monitoring indicator based on the Mahalanobis distance; When the similarity is less than a preset similarity threshold, it is determined that the running state of the target instance has not changed.
[0052] Specifically, when the target instance triggers self-healing for the first time, the current first monitoring indicator will be recorded in the cache. When the target instance triggers self-healing again within a short period of time, the new second monitoring indicator will be compared with the first monitoring indicator in the cache for similarity. If the two monitoring indicators are judged to be similar, it is considered that the first self-healing has no positive impact on the system and the self-healing is invalid, so the second self-healing request is rejected and the corresponding status code is returned.
[0053] If the two monitoring indicators are different, the instance will be restarted according to the normal self-healing rules, and the triggering conditions will be recorded in the cache. The triggering condition data in the cache can be set to have a validity period. If the validity period exceeds the validity period, no verification will be performed before the instance self-heals. The validity period can be set longer than the general prohibition of self-healing validity period. In this way, the instance can be prevented from self-healing repeatedly due to the same reason, and the instance self-healing function can be kept alive, and instance failures caused by other reasons can be automatically resolved through self-healing means.
[0054] Method for determining the similarity between the first monitoring indicator and the second monitoring indicator: The indicators involved in instance self-healing have different dimensions and importance, so the Weighted Mahalanobis Distance can be used as a basis for determining the similarity between the two groups of monitoring indicators.
[0055] ; ; in, x, y Represents the time between the two self-healing triggers n Item monitoring indicator data, k is the weight of different indicators, σ for x The covariance of is the index of n. Different thresholds are set for the similarity of trigger conditions according to different instance categories.
[0056] In one embodiment, the method further includes: after the target instance performs a self-healing operation, performing a self-healing check on the target instance, and if it is determined that the self-healing of the target instance is not invalid, repeatedly performing the self-healing operation of the target instance.
[0057] When it is determined that the self-healing of the target instance is not an invalid self-healing, the self-healing operation of the target instance is repeatedly performed to implement the self-healing process of the target instance.
[0058] The present invention also provides a schematic diagram of a device structure for applying the method for identifying invalid self-healing provided by the present invention, as shown in FIG. Figure 2 As shown, the device includes: a metric collector (Metric Collector, MC), a connectivity tester (Connectivity Tester, CT), an anomaly detector (Anomaly Detector, AD), an instance status verifier (Instance Status Verifier, ISV), and a contingency plan executor (Contingency Plan Actuator, CPA).
[0059] Metric Collector (MC): used to observe the health of the instance itself as a key indicator for triggering instance self-healing. It collects instance indicators such as the number of threads, GC, memory usage, and database connection status into a unified time series database.
[0060] Connectivity Tester (CT): Periodically detects the connectivity and service availability of instances as one of the auxiliary indicators of instance abnormalities to prevent the occurrence of a situation where the instance itself is performing normally but self-healing is not triggered when external services are abnormal. The instance connectivity indicators are also stored in the time series database.
[0061] Anomaly Detector (AD): The brain of the monitoring system. It compares the preset thresholds with the instance indicators and combines other indicators such as instance connectivity to determine the instance health status. It then determines whether the instance needs to be automatically restarted, i.e. self-healing, based on the preset logic.
[0062] Instance Status Verifier (ISV): An instance status verifier (ISV) is added between AD and CPA to review self-healing requests to prevent unexpected self-healing. ISV uses the communication log of the remote control port to determine whether the instance is in a state of manual intervention to prevent the instance from being mistakenly self-healed during manual intervention; at the same time, after a self-healing, ISV will compare the monitoring indicators before and after the instance self-healing to determine whether the last self-healing was effective. If the last self-healing did not change the health status of the instance, the subsequent self-healing requests of the instance will be prohibited to prevent the instance from entering a state of cyclic self-healing.
[0063] Contingency Plan Actuator (CPA): Different instance types have different self-healing methods. Its core purpose is to restore the instance to its initial state by restarting or rebuilding the instance, thereby resolving failures caused by the instance's own abnormalities. For example, for virtual machines, the self-healing plan is generally to execute a preset script; for containers, the container platform destroys the abnormal container for the abnormal process and pulls up a new container.
[0064] Specifically, the purpose of the instance controlled state check is to determine whether the instance is currently under human command. In this case, even if the instance is determined to be abnormal by the anomaly detector, it should not be self-healed to avoid interrupting the normal operation process.
[0065] Whether you log in to the instance manually through remote login, manage the virtual machine through the control node, or manage the container cluster through the cloud platform, the underlying implementation method is basically SSH or Telnet. Therefore, the instance's controlled status can be determined by monitoring the instance's login and operation logs. Figure 3As shown in the schematic diagram of the instance controlled determination process provided by the present invention, when the instance status verifier monitors a self-healing request, it actively obtains the acct, sudolog, lastlog, utmp and other logs of the instance within a certain period of time. When the operation log indicates that instructions have been issued to the instance within a certain period of time, the anomaly detector determines that the current instance host is in a controlled state, and at the same time rejects the self-healing request and returns the corresponding status code to the anomaly detector AD.
[0066] The purpose of the instance status check before and after self-healing is to optimize the self-healing trigger logic and determine whether the system problem can be fixed after the first self-healing. If it cannot be fixed, no self-healing will be performed to prevent the instance from entering a state of cyclic restart. For example, when a database anomaly causes the instance thread connecting to the data to be blocked, restarting (self-healing) the instance does not solve the database problem. Instead, the service is completely interrupted because the instance is stuck in a cyclic restart.
[0067] like Figure 4 As shown in the flow diagram of the status verification before and after the self-healing of the instance provided by the present invention, when the instance triggers self-healing for the first time, the current trigger condition will be recorded in the cache. When the instance triggers self-healing again in a short period of time, the ISV compares the new trigger condition with the trigger condition in the cache for similarity. If the ISV determines that the two trigger conditions are similar, it is considered that the first self-healing has no positive impact on the system and the self-healing is invalid, so the second self-healing request is rejected and the corresponding status code is returned to the anomaly detector. If the ISV determines that the two self-healing trigger conditions are different, the instance is restarted according to the normal self-healing rules, and the trigger condition is recorded in the cache. The trigger condition data in the cache can be set with an effective period. If the effective period is exceeded, no verification will be performed before the instance self-heals. The setting duration of the validity period can be longer than the general prohibition of self-healing validity period. In this way, the instance can be prevented from repeatedly self-healing due to the same reason, and the instance self-healing function can be kept alive, and instance failures caused by other reasons can be automatically resolved by self-healing means.
[0068] The following is a description of the example invalid self-healing identification device provided by the present invention. The example invalid self-healing identification device described below and the example invalid self-healing identification method described above can be referred to each other. Figure 5 As shown, the device comprises: A judgment module 510 is used to judge the running state of the target instance and determine whether the target instance needs to perform a self-healing operation; A verification module 520 is used to perform a self-healing verification on the target instance after the target instance performs a self-healing operation, and if it is determined that the self-healing of the target instance is invalid, exit the self-healing operation of the target instance; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
[0069] The device for identifying invalid self-healing of an instance provided by the present invention reviews the self-healing request to determine whether the current self-healing conflicts with human operation, and also determines whether the current self-healing can solve the problem of the current instance, thereby avoiding the occurrence of invalid self-healing and avoiding the possibility that the fundamental reason for the instance triggering self-healing is not caused by the instance itself, resulting in repeated self-healing of the instance, causing system shock, and causing serious consequences such as self-healing collapse of the system, thereby improving the stability of system operation.
[0070] In one embodiment, the determination module 510 is specifically used to: The judging the running state of the target instance and determining that the target instance needs to perform a self-healing operation includes: Based on the key indicators of the target instance that trigger instance self-healing, determine that the operating indicators of the target instance are abnormal, where the key indicators include one or more of the number of threads of the target instance, garbage collection information of the target instance, memory usage of the target instance, and database connection information of the target instance; Detecting the connectivity of the target instance and the service availability of the target instance to determine that the target instance is operating abnormally; Based on the abnormality of the operating indicator of the target instance and the abnormal operation of the target instance, it is determined that the target instance needs to perform a self-healing operation.
[0071] In one embodiment, the verification module 520 is specifically used to: Determining that the target instance is in a human intervention state includes: Obtaining log data of the target instance within a preset time period; The log data is analyzed, and when it is determined that the log data contains remote login protocol information or the log data contains remote access protocol information, it is determined that the target instance is in a manual intervention state.
[0072] In one embodiment, the verification module 520 is further specifically configured to: Determine that the running status of the target instance does not change before and after self-healing, including: Obtaining a first monitoring indicator before the target instance is self-healed and a second monitoring indicator after the target instance is self-healed; The first monitoring indicator is compared with the second monitoring indicator to determine that the running state of the target instance has not changed.
[0073] In one embodiment, the verification module 520 is further specifically configured to: Comparing the first monitoring indicator with the second monitoring indicator to determine that the running state of the target instance has not changed includes: Determine the similarity between the first monitoring indicator and the second monitoring indicator based on the Mahalanobis distance; When the similarity is less than a preset similarity threshold, it is determined that the running state of the target instance has not changed.
[0074] In one embodiment, the verification module 520 is further specifically configured to: After the target instance performs a self-healing operation, a self-healing check is performed on the target instance. If it is determined that the self-healing of the target instance is not invalid self-healing, the self-healing operation of the target instance is repeatedly performed.
[0075] Figure 6 An example of a physical structure diagram of an electronic device is shown in FIG. Figure 6 As shown, the electronic device may include: a processor 610, a communication interface 620, a memory 630 and a communication bus 640, wherein the processor 610, the communication interface 620 and the memory 630 communicate with each other through the communication bus 640. The processor 610 may call the logic instructions in the memory 630 to execute the method for identifying invalid self-healing of an instance, the method comprising: judging the running state of the target instance, and determining that the target instance needs to perform a self-healing operation; After the target instance performs a self-healing operation, performing a self-healing check on the target instance, and if it is determined that the self-healing of the target instance is invalid, exiting the self-healing operation of the target instance; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
[0076] In addition, the logic instructions in the above-mentioned memory 630 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.
[0077] On the other hand, the present invention further provides a computer program product, the computer program product includes a computer program, the computer program can be stored in a non-transitory computer-readable storage medium, when the computer program is executed by a processor, the computer can execute the instance invalid self-healing identification method provided by the above methods, the method includes: judging the running state of the target instance, determining that the target instance needs to perform a self-healing operation; After the target instance performs a self-healing operation, performing a self-healing check on the target instance, and if it is determined that the self-healing of the target instance is invalid, exiting the self-healing operation of the target instance; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
[0078] In another aspect, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which is implemented when the computer program is executed by a processor to perform the method for identifying invalid self-healing of an instance provided by the above methods, the method comprising: judging the running state of a target instance, and determining that the target instance needs to perform a self-healing operation; After the target instance performs a self-healing operation, performing a self-healing check on the target instance, and if it is determined that the self-healing of the target instance is invalid, exiting the self-healing operation of the target instance; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
[0079] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art may understand and implement it without creative effort.
[0080] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.
[0081] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A method for identifying invalid self-healing of an instance, characterized in that: The method comprises: Determine the running status of the target instance and determine whether the target instance needs to perform a self-healing operation; After the target instance performs a self-healing operation, performing a self-healing check on the target instance, and if it is determined that the self-healing of the target instance is invalid, exiting the self-healing operation of the target instance; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
2. The method for identifying invalid self-healing of an instance according to claim 1, characterized in that: The judging the running state of the target instance and determining that the target instance needs to perform a self-healing operation includes: Based on the key indicators of the target instance that trigger instance self-healing, determine that the operating indicators of the target instance are abnormal, where the key indicators include one or more of the number of threads of the target instance, garbage collection information of the target instance, memory usage of the target instance, and database connection information of the target instance; Detecting the connectivity of the target instance and the service availability of the target instance to determine that the target instance is operating abnormally; Based on the abnormality of the operating indicator of the target instance and the abnormal operation of the target instance, it is determined that the target instance needs to perform a self-healing operation.
3. The method for identifying invalid self-healing of an instance according to claim 1, characterized in that: The determining that the target instance is in a human intervention state includes: Obtaining log data of the target instance within a preset time period; The log data is analyzed, and when it is determined that the log data contains remote login protocol information or the log data contains remote access protocol information, it is determined that the target instance is in a manual intervention state.
4. The method for identifying invalid self-healing of an instance according to claim 1, characterized in that: The determining that the running state of the target instance does not change before and after the self-healing includes: Obtaining a first monitoring indicator before the target instance is self-healed and a second monitoring indicator after the target instance is self-healed; The first monitoring indicator is compared with the second monitoring indicator to determine that the running state of the target instance has not changed.
5. The method for identifying invalid self-healing of an instance according to claim 4, characterized in that: The comparing the first monitoring indicator with the second monitoring indicator to determine that the running state of the target instance has not changed includes: Determine the similarity between the first monitoring indicator and the second monitoring indicator based on the Mahalanobis distance; When the similarity is less than a preset similarity threshold, it is determined that the running state of the target instance has not changed.
6. The method for identifying invalid self-healing of an instance according to claim 1, characterized in that: Also includes: After the target instance performs a self-healing operation, a self-healing check is performed on the target instance. If it is determined that the self-healing of the target instance is not invalid, the self-healing operation of the target instance is repeatedly performed.
7. An instance invalid self-healing identification device, characterized in that: include: A judgment module, used to judge the running state of the target instance and determine whether the target instance needs to perform a self-healing operation; A verification module, configured to perform a self-healing verification on the target instance after the target instance performs a self-healing operation, and to exit the self-healing operation of the target instance if it is determined that the self-healing of the target instance is invalid; Determining that the self-healing of the target instance is invalid self-healing includes: It is determined that the target instance is in a manual intervention state, or it is determined that the running state of the target instance does not change before and after self-healing.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for identifying invalid self-healing according to any one of claims 1 to 6 is implemented.
9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for identifying invalid self-healing according to any one of claims 1 to 6 is implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method for identifying invalid self-healing according to any one of claims 1 to 6 is implemented.