Information processing method, device, apparatus, system, and storage medium

Abstract

Embodiments of the present application provide an information processing method, device, apparatus, system and storage medium. In the embodiments of the present application, the occurrence of a fault is perceived from the perspective of a service instance. Specifically, a service instance and a target service are deployed on a server device. Each service instance reports its working state information and service dependency information to the target service. The target service reports the service dependency information to a monitoring service center. The target service can discover a first service instance that has a fault in time according to the reported working state information, thereby providing a basis for subsequent fault processing. Meanwhile, the target service sends notification information to the monitoring service center. The monitoring service center can timely notify other service instances that have a dependency relationship with the first service instance, thereby avoiding a chain reaction caused by the occurrence of the fault of the first service instance and preventing the loss from being expanded.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to an information processing method, device, apparatus, system and storage medium. Background Technology

[0002] In current software service architectures and deployments, a complete application service often requires the deployment of several critical foundational services and single-function services. Each application service needs to be deployed with multiple service instances to ensure stability and high availability. However, computer software and hardware have a certain failure rate, which may lead to downtime or equipment damage, thus affecting the normal operation of the software service. Therefore, a fault handling solution is needed for each service instance. Summary of the Invention

[0003] This application provides an information processing method, apparatus, device, system, and storage medium for sensing service instance-level faults.

[0004] This application provides an information processing method applicable to an information processing system. The information processing system includes at least one server-side device. For any server-side device, the method includes: acquiring service dependency information reported by each service instance in the server-side device and providing it to a monitoring service center in the information processing system; acquiring working status information reported by each service instance on the server-side device; when a first service instance that has failed is identified based on the working status information, sending a first notification message to the monitoring service center to indicate that the first service instance has failed, so that the monitoring service center can determine at least one second service instance on the server-side device that has a dependency relationship with the first service instance based on the service dependency information of each service instance provided by the server-side device and the first notification message, and sending a second notification message to the second service instance to instruct the second service instance to terminate the dependency relationship with the first service instance.

[0005] This application also provides an information processing method applicable to a monitoring service center in an information processing system. The method includes: receiving service dependency information and first notification information reported by each server device in the information processing system between service instances, wherein the first notification information is used to indicate that a first service instance has failed; determining, based on the service dependency information and the first notification information, a second service instance on each server device that has a dependency relationship with the first service instance, and sending a second notification information to the second service instance to indicate that the second service instance ends its dependency relationship with the first service instance, and sending a second notification information to the second service instance to indicate that the second service instance ends its dependency relationship with the first service instance.

[0006] This application also provides an information processing system, including: at least one server-side device and a monitoring service center. Each server-side device is deployed with multiple service instances and a target service. Multiple service instances are used to report their own working status information and service dependency information between themselves and other service instances to the target service on their respective server-side devices. A target service is used to receive the service dependency information reported by each service instance and provide it to the monitoring service center, and to receive the working status information reported by each service instance on its own server-side device. When a first service instance that has failed is identified based on the working status information, the target service sends a first notification message to the monitoring service center to indicate that the first service instance has failed. The monitoring service center is used to determine at least one second service instance on the server-side device that has a dependency relationship with the first service instance based on the service dependency information and the first notification message provided by the target service, and to send a second notification message to the second service instance to instruct the second service instance to terminate its dependency relationship with the first service instance.

[0007] This application embodiment also provides a server-side device, including: an acquisition module and a sending module; the acquisition module is used to acquire service dependency information reported by each service instance in the server-side device and provide it to a monitoring service device in an information processing system, and to acquire working status information reported by each service instance on the server-side device; the sending module is used to send a first notification message to the monitoring service device to indicate that the first service instance has failed when a first service instance is identified as having failed based on the working status information, so that the monitoring service device can determine a second service instance that has a dependency relationship with the first service instance based on the service dependency information of each service instance provided by the server-side device and the first notification message, and send a second notification message to the second service instance to indicate that the second service instance ends its dependency relationship with the first service instance.

[0008] This application embodiment also provides a monitoring service device, including: a receiving module, a determining module, and a sending module; the receiving module is used to receive service dependency information and first notification information reported by each server device in the information processing system between service instances, the first notification information being used to indicate that a first service instance has failed; the determining module is used to determine, based on the service dependency information and the first notification information, a second service instance on each server device that has a dependency relationship with the first service instance; the sending module is used to send a second notification information to the second service instance to indicate that the second service instance ends its dependency relationship with the first service instance.

[0009] This application also provides a server device, including: a memory and a processor; the memory for storing computer programs; and the processor, coupled to the memory, for executing the computer programs to implement the steps in the information processing method provided in this application.

[0010] This application also provides a monitoring service device, including: a memory and a processor; the memory for storing computer programs; and the processor, coupled to the memory, for executing the computer programs to implement the steps in the information processing method provided in this application.

[0011] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, causes the processor to implement the steps in the information processing method provided in this application.

[0012] This application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps in the information processing method provided in this application.

[0013] The technical solutions provided by the embodiments of this disclosure bring at least the following beneficial effects: The occurrence of faults is perceived from the perspective of service instances. Specifically, service instances and target services are deployed on the server-side device. Each service instance reports its working status information and service dependency information to the target service. The target service reports its service dependency information to the monitoring service center. Based on the reported working status information, the target service can promptly identify the first service instance that has failed, providing a basis for subsequent fault handling. At the same time, it sends notification information to the monitoring service center, which can promptly notify other service instances that have dependencies on the first service instance, avoiding a chain reaction caused by the failure of the first service instance and preventing the expansion of losses.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0016] Figure 1 A schematic diagram of the structure of an information processing system provided for an exemplary embodiment of this application;

[0017] Figure 2 A flowchart illustrating an information processing method provided for an exemplary embodiment of this application;

[0018] Figure 3 A flowchart illustrating another information processing method provided for an exemplary embodiment of this application;

[0019] Figure 4 A schematic diagram of the structure of a server device provided for an exemplary embodiment of this application;

[0020] Figure 5 A schematic diagram of the structure of a monitoring service device provided for an exemplary embodiment of this application;

[0021] Figure 6 A schematic diagram of the structure of a server device provided for an exemplary embodiment of this application;

[0022] Figure 7 This is a schematic diagram of the structure of a monitoring service device provided as an exemplary embodiment of this application. Detailed Implementation

[0023] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0024] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0025] To address the potential for system crashes or equipment damage in existing technologies, this application embodiment detects faults from the perspective of service instances. Specifically, service instances and target services are deployed on the server-side device. Each service instance reports its own operational status information and service dependency information to the target service. The target service reports its service dependency information to the monitoring service center. Based on its reported operational status information, the target service can promptly identify the first service instance that has failed, providing a foundation for subsequent fault handling. Simultaneously, it sends a notification to the monitoring service center, which can promptly notify other service instances that depend on the first service instance, preventing a chain reaction caused by the failure of the first service instance and thus avoiding the expansion of losses.

[0026] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0027] Figure 1 This is a schematic diagram of the structure of an information processing system provided for an exemplary embodiment of this application. For example... Figure 1 As shown, the system 100 includes: at least one server device 10, and each server device 10 has multiple service instances 101 and target services 102 deployed on it.

[0028] In this embodiment, each application service requires the deployment of multiple service instances 101 to ensure stability and high availability. Application services can be, but are not limited to, online education services, video services, game services, or email services. An application service can be implemented as a group of service instances 101, with each service instance 101 deployed on a server-side device 10 in the form of a container or virtual machine. The server-side device 10 can be a conventional server, a cloud server, or a server array. Multiple service instances 101 can be deployed on each server-side device 10; these multiple service instances 101 can originate from the same application service or from different application services.

[0029] In this embodiment, in addition to deploying multiple service instances 101, each server device 10 also deploys a target service 102. The target service 102 is used to detect whether the service instances 101 are malfunctioning. Based on this, multiple service instances 101 can report their own working status information to the target service 102 on their respective server device 10. The working status information can indicate that the service instance is in a working state, for example, the service instance is in a normal operating state, or the working status information can also indicate that the service instance is in a fault state, for example, the service instance is stuck, abnormal, or malfunctioning.

[0030] In this embodiment, the target service 102 can receive the working status information reported by each service instance 101, and identify whether any service instance in each service instance 101 has failed based on the working status information. For ease of distinction and description, the service instance in each service instance 101 that has failed is referred to as the first service instance. The number of first service instances can be one or more.

[0031] Optionally, multiple service instances 101 can send registration requests to the target service 102 on their respective server devices 10 to register for services, and upon successful registration, report their own operational status information to the target service 102. The registration request includes at least the identification information of the service instance 101, such as the name of the service instance or the application service to which the service instance belongs. Correspondingly, the target service 102 can receive the registration requests sent by each service instance 101 on its server device 10, register each service instance 101 according to the registration requests, and upon successful registration of each service instance 101, receive the operational status information reported by each service instance 101, and identify whether any service instances among the service instances 101 have experienced a failure based on the operational status information.

[0032] In this embodiment, faults can be detected at the service instance level. Specifically, each service instance registers with the target service on its server device. Upon successful registration, it reports its own operational status information to the target service. The target service then identifies, based on the received operational status information, whether a first service instance among the service instances has experienced a fault. Throughout this process, the target service can promptly detect faults at the service instance level, providing a foundation for subsequent fault handling.

[0033] Furthermore, in addition to including at least one server device 10, the information processing system 100 also includes, for example... Figure 1 As shown, the information processing system 100 also includes a monitoring service center 20. The monitoring service center 20 is used to send a notification message to a second service instance that has a dependency on the first service instance when the target service 102 detects a failure in the first service instance. This notification informs the second service instance to terminate its dependency on the first service instance. Throughout this process, service instance failures can be detected promptly, and the second service instance that depends on the failed first service instance can also be aware of the failure, preventing a chain reaction caused by the failure of the first service instance and thus avoiding further losses.

[0034] The number of second service instances can be one or more. The second service instance and the first service instance can be deployed on the same server device 10 or on different server devices 10. Furthermore, the dependencies between service instances 101 can refer to the mutual invocation relationships between service instances 101 or the relationships requiring interaction between service instances 101. These dependencies can be represented by service dependency information, which includes information about mutual invocation relationships or the relationships requiring interaction between service instances 101.

[0035] Specifically, the multiple service instances 101 are further configured to: report service dependency information between themselves and other service instances 101 to the target service 102. The target service 102 receives the service dependency information reported by each service instance 101 and provides it to the monitoring service center 20. Upon identifying a first service instance that has failed, the target service 102 sends a first notification message to the monitoring service center 20 indicating that the first service instance has failed, such as... Figure 1As shown. Based on the service dependency information of each service instance 101 provided by the target service and the first notification information, the monitoring service center 20 determines at least one second service instance on the server-side device 10 that has a dependency relationship with the first service instance, and sends a second notification information to the second service instance to instruct it to terminate its dependency relationship with the first service instance. The implementation method of the monitoring service center 20 sending the second notification information to the second service instance is not limited. For example, the monitoring service center 20 can directly send the second notification information to the second service instance on the server-side device 10, or the monitoring service center 20 can send the second notification information to the target service of the server-side device where the second service instance is located, and the target service can then distribute the second notification information to the second service instance.

[0036] In an optional embodiment, when the target service 102 identifies a first service instance that has failed among the service instances 101 based on the working status information, the target service 102 can also perform operations such as restarting the first service instance that has failed to attempt automated fault recovery. Figure 1 As shown by the dashed line. Automated fault repair avoids the problem of excessively long fault recovery times caused by manual intervention. Simultaneously, automated fault recovery reduces the workload and management costs of manual repair, allowing some faults that can be automatically recovered to be handled without manual intervention. Specifically, target service 102 uses a restart method to automatically recover the first service instance from faults. The implementation method of using a restart method to automatically recover the first service instance from faults is not limited. For example, if the first service instance is running, it is shut down and then restarted; if the first service instance is not running, it is directly started. Furthermore, target service 102 can monitor whether the first service instance has recovered from the fault after restarting. If the first service instance has recovered from the fault after restarting, it sends a third notification message to monitoring service center 20 to indicate that the first service instance has recovered from the fault. Monitoring service center 20 then sends a fourth notification message to the second service instance to instruct the second service instance to re-establish the dependency relationship with the first service instance. Optionally, if the first service instance fails to recover after restarting, the target service 102 sends a fifth notification message to the monitoring service center 20, indicating that the first service instance has not recovered, so that the monitoring service center 20 can notify the maintenance node to repair the first service instance. Notifying the maintenance node to repair the first service instance can be understood as notifying administrators to manually repair the first service instance.

[0037] In an optional embodiment, each service instance 101 is further configured to periodically report its working status information to the target service 102; correspondingly, the target service 102 can also analyze the working status of the corresponding service instance based on the working status information reported by each service instance 101; the service instance 101 whose working status information indicates a service failure is designated as the first service instance, or the service instance 101 that has not reported working status information within a set first time threshold is designated as the first service instance.

[0038] Optionally, the target service 102 deployed on at least one server-side device 10 is further configured to: periodically report the working status information of multiple service instances to the monitoring service center 20. The monitoring service center 20 can also monitor whether there is a first target service that has not reported the working status information of multiple service instances within a set second time threshold; if a first target service that has not reported the working status information of multiple service instances is detected within the set second time threshold, it is determined that the first server-side device where the first target service is located has a service failure, and based on the service dependency information of each service instance, a third service instance that has a dependency relationship with any service instance on the first server is determined, and a sixth notification message is sent to the third service instance to instruct the third service instance to end its dependency relationship with the service instance on the first server; and the maintenance node is notified to repair the fault on the server where the first target service is located.

[0039] Optionally, the target service 102 can also detect whether the first server device has recovered from the fault. If the first server device has recovered from the fault, it sends a seventh notification message to the monitoring service center 20. Upon receiving the seventh notification message, the monitoring service center 20 sends an eighth notification message to the third service instance that depends on the service instance on the first server device, instructing the third service instance to re-establish the dependency relationship with the service instance on the first server device.

[0040] By monitoring the working status information of service instances, it detects whether a service instance has encountered an anomaly or failure. If an anomaly or failure occurs, it notifies other service instances, based on service dependencies, to stop calling the failed service instance. This involves obtaining the service dependency information of the service instance.

[0041] In this embodiment, service instances and a target service are deployed on each server-side device. The target service can detect the occurrence and recovery of faults in each service instance on its server-side device. Since the target service and service instances are deployed on the same server-side device, the target service can directly perform automated fault recovery, such as restarting the faulty service instance. While performing fault recovery or detecting service instance fault recovery, the target service reports changes in the service instance's working status information to the monitoring service center. Furthermore, the target service can obtain service dependency information for each service instance on its server-side device. Based on this service dependency information, other service instances that depend on the service instance whose working status has changed can promptly detect the change in working status. In addition, the target service continuously monitors the results of automated fault recovery, and the monitoring service center continuously monitors the target service, enabling it to promptly detect the occurrence of faults that cannot be automatically recovered and to promptly notify maintenance nodes for handling.

[0042] Based on the aforementioned information processing system, this application also provides an information processing method applicable to the information processing system, which includes at least one server-side device. For any server-side device, such as... Figure 2 As shown, the method includes:

[0043] 201. Obtain the service dependency information reported by each service instance in the server-side device and provide it to the monitoring service center in the information processing system;

[0044] 202. Obtain the working status information reported by each service instance on the server device;

[0045] 203. When a first service instance that has failed is identified based on the working status information, a first notification message is sent to the monitoring service center to indicate that the first service instance has failed. This allows the monitoring service center to determine at least one second service instance on the server that has a dependency relationship with the first service instance based on the service dependency information of each service instance provided by the server device and the first notification message. The monitoring service center then sends a second notification message to the second service instance to instruct the second service instance to terminate its dependency relationship with the first service instance.

[0046] In an optional embodiment, the method provided in this application further includes: automatically recovering the first service instance from failure by restarting, and monitoring whether the first service instance recovers from failure after restarting; if the first service instance recovers from failure after restarting, sending a third notification message to the monitoring service center to indicate that the first service instance has recovered from failure, so that the monitoring service center can send a fourth notification message to the second service instance indicating that the first service instance has recovered from failure, the fourth notification message being used to instruct the second service instance to re-establish the dependency relationship with the first service instance.

[0047] In an optional embodiment, the method provided in this application further includes: if the first service instance fails to recover after restarting, sending a fifth notification message to the monitoring service center to indicate that the first service instance has not recovered, so that the monitoring service center can notify the maintenance node to repair the first service instance.

[0048] In an optional embodiment, the method provided in this application further includes: analyzing the working status information of the corresponding service instances based on the working status information reported by each service instance; taking the service instance whose working status information indicates a service failure as the first service instance, or taking the service instance that has not reported working status information within a set first time threshold as the first service instance.

[0049] In an optional embodiment, the method provided in this application further includes: periodically reporting the working status information of each service instance to the monitoring service center, so that the monitoring service center can monitor whether there is a first server device that has not reported the working status information of multiple service instances within a set second time threshold.

[0050] In an optional embodiment, the method provided in this application further includes: if the fault of the first server device is recovered, a seventh notification message of the fault recovery of the first server device is sent to the monitoring service center, so that the monitoring service center can send an eighth notification message to the third service instance that depends on the service instance on the first server device, and the eighth notification message is used to instruct the third service instance to re-establish the dependency relationship with the service instance on the first server device.

[0051] Based on the aforementioned information processing system, this application embodiment also provides another information processing method, applicable to a monitoring service center within the information processing system, such as... Figure 3 As shown, the method includes:

[0052] 301. Receive service dependency information and first notification information between service instances reported by each server device in the information processing system. The first notification information is used to indicate that the first service instance has failed.

[0053] 302. Based on the service dependency information and the first notification information, determine the second service instance on each server device that has a dependency relationship with the first service instance, and send the second notification information to the second service instance to instruct the second service instance to end the dependency relationship with the first service instance.

[0054] In an optional embodiment, the method provided in this application further includes: receiving working status information of multiple service instances sent periodically by each server device; monitoring whether there is a first server device that has not reported the working status information of multiple service instances within a set second time threshold; if so, determining that the first server device has experienced a service failure, and determining a third service instance that has a dependency relationship with any service instance on the first server device based on the service dependency information of each service instance.

[0055] In an optional embodiment, the method provided in this application further includes: when it is determined that the first server device has a service failure, sending a sixth notification message to the third service instance to instruct the third service instance to end its dependency on the service instance on the first server device; and notifying the maintenance node to repair the first server device.

[0056] In an optional embodiment, the method provided in this application further includes: receiving a seventh notification message from the first server device indicating that the first server device has recovered from a fault; and sending an eighth notification message to the third service instance based on the seventh notification message to instruct the third service instance to re-establish the dependency relationship between the third service instance and the service instance on the first server device.

[0057] It should be noted that the execution subject of each step of the method provided in the above embodiments can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 201 to 202 can be device A; or the execution subject of step 201 can be device A, and the execution subject of step 202 can be device B; and so on.

[0058] Furthermore, in some of the processes described in the above embodiments and accompanying drawings, multiple operations appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear herein, or they may be executed in parallel. The operation numbers, such as 201, 202, etc., are merely used to distinguish different operations and do not represent any execution order. Additionally, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel. It should be noted that the descriptions such as "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., and do not represent a sequential order, nor do they limit "first" and "second" to different types.

[0059] Figure 4 This is a schematic diagram of the structure of a server device provided for an exemplary embodiment of this application. For example... Figure 4 As shown, the device includes a memory 44 and a processor 45.

[0060] Memory 44 is used to store computer programs and can be configured to store various other data to support operation on the server device. Examples of this data include instructions for any application or method used to operate on the server device.

[0061] The memory 44 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0062] The processor 45, coupled to the memory 44, is used to execute a computer program in the memory 44 for: acquiring service dependency information reported by each service instance in the server device and providing it to the monitoring service center in the information processing system; acquiring working status information reported by each service instance on the server device; and when a first service instance that has failed is identified based on the working status information, sending a first notification message to the monitoring service center to indicate that the first service instance has failed, so that the monitoring service center can determine at least one second service instance on the server device that has a dependency relationship with the first service instance based on the service dependency information of each service instance provided by the server device and the first notification message, and sending a second notification message to the second service instance to indicate that the second service instance ends its dependency relationship with the first service instance.

[0063] In an optional embodiment, the processor 45 is further configured to: perform automated fault recovery on the first service instance using a restart method, and monitor whether the first service instance recovers from the fault after restarting; if the first service instance recovers from the fault after restarting, send a third notification message to the monitoring service center to indicate that the first service instance has recovered from the fault, so that the monitoring service center can send a fourth notification message to the second service instance indicating that the first service instance has recovered from the fault, the fourth notification message being used to instruct the second service instance to re-establish the dependency relationship with the first service instance.

[0064] In an optional embodiment, the processor 45 is further configured to: if the first service instance fails to recover after restarting, send a fifth notification message to the monitoring service center indicating that the first service instance has not recovered, so that the monitoring service center can notify the maintenance node to repair the first service instance.

[0065] In an optional embodiment, the processor 45 is further configured to: analyze the working status of the corresponding service instance based on the working status information reported by each service instance; and designate the service instance whose working status information indicates a service failure as the first service instance, or designate the service instance that has not reported working status information within a set first time threshold as the first service instance.

[0066] In an optional embodiment, the processor 45 is further configured to: periodically report the working status information of each service instance to the monitoring service center, so that the monitoring service center can monitor whether there is a first server device that has not reported the working status information of multiple service instances within a set second time threshold.

[0067] In an optional embodiment, the processor 45 is further configured to: if the first server device recovers from the failure, send a seventh notification message of the first server device failure recovery to the monitoring service center, so that the monitoring service center can send an eighth notification message to the third service instance that depends on the service instance on the first server device, the eighth notification message being used to instruct the third service instance to re-establish the dependency relationship with the service instance on the first server device.

[0068] The server-side device provided in this application embodiment perceives the occurrence of faults from the perspective of service instances. Specifically, the server-side device is deployed with service instances and target services. Each service instance reports its own working status information and service dependency information to the target service. The target service reports service dependency information to the monitoring service center. The target service can promptly discover the first service instance that has failed based on its reported working status information, providing a basis for subsequent fault handling. At the same time, it sends notification information to the monitoring service center. The monitoring service center can promptly notify other service instances that have dependencies on the first service instance, avoiding a chain reaction caused by the failure of the first service instance and preventing the expansion of losses.

[0069] Furthermore, such as Figure 4 As shown, the server-side device also includes other components such as a communication component 46 and a power supply component 48. Figure 4 The diagram only shows a portion of the components and does not imply that the server-side device only includes... Figure 4 The components shown.

[0070] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to perform... Figure 2 The steps in the method shown.

[0071] Accordingly, embodiments of this application also provide a computer program product, including a computer program / instructions, which, when executed by a processor, can achieve... Figure 2 The steps in the method shown.

[0072] Figure 5 This is a schematic diagram of the structure of a monitoring service device provided as an exemplary embodiment of this application. Figure 5 As shown, the device includes a memory 54 and a processor 55.

[0073] Memory 54 is used to store computer programs and can be configured to store various other data to support operation on the monitoring service device. Examples of this data include instructions for any application or method used to operate on the monitoring service device.

[0074] The memory 54 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0075] The processor 56, coupled to the memory 54, is used to execute a computer program in the memory 54 for: receiving service dependency information and first notification information between service instances reported by each server device in the information processing system, wherein the first notification information is used to indicate that a first service instance has failed; determining, based on the service dependency information and the first notification information, a second service instance on each server device that has a dependency relationship with the first service instance, and sending a second notification information to the second service instance to indicate that the second service instance ends its dependency relationship with the first service instance.

[0076] In an optional embodiment, the processor 55 is further configured to: receive working status information of multiple service instances sent periodically by each server device; monitor whether there is a first server device that has not reported working status information of multiple service instances within a set second time threshold; if so, determine that the first server device has a service failure, determine a third service instance that has a dependency relationship with any service instance on the first server device according to the service dependency information of each service instance, and send a sixth notification message to the third service instance to instruct the third service instance to end its dependency relationship with the service instance on the first server device.

[0077] In an optional embodiment, the processor 55 is further configured to: notify the maintenance node to repair the first server device when it is determined that the first server device has experienced a service failure.

[0078] In an optional embodiment, the processor 55 is further configured to: receive a seventh notification message from the first server device indicating that the first server device has recovered from a fault; and, based on the seventh notification message, send an eighth notification message to the third service instance to instruct the third service instance to re-establish the dependency relationship between the third service instance and the service instance on the first server device.

[0079] Furthermore, such as Figure 5 As shown, the monitoring service equipment also includes other components such as communication component 56, display 57, power supply component 58, and audio component 59. Figure 5 The diagram only shows a portion of the components and does not imply that the monitoring service equipment includes only these components. Figure 5 The components shown. It should be noted that... Figure 5 The components within the dashed box are optional, not mandatory, and their specific requirements depend on the product type of the monitoring service equipment.

[0080] Accordingly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to perform... Figure 3 The steps in the method shown.

[0081] Accordingly, embodiments of this application also provide a computer program product, including a computer program / instructions, which, when executed by a processor, can achieve... Figure 3 The steps in the method shown.

[0082] Figure 6 This application provides a schematic diagram of the structure of a server device, which can be implemented as a server-side device in an information processing system, such as... Figure 6 As shown, the server device includes an acquisition module 61 and a sending module 62.

[0083] The acquisition module 61 is used to acquire the service dependency information reported by each service instance in the server device and provide it to the monitoring service device in the information processing system, as well as to acquire the working status information reported by each service instance on the server device.

[0084] The sending module 62 is used to send a first notification message to the monitoring service device to indicate that the first service instance has failed when the first service instance is identified as having failed based on the working status information. This allows the monitoring service device to determine the second service instance that has a dependency relationship with the first service instance based on the service dependency information of each service instance provided by the server device and the first notification message, and to send a second notification message to the second service instance to instruct the second service instance to end the dependency relationship with the first service instance.

[0085] In one optional embodiment, the server-side device further includes: a recovery module and a monitoring module;

[0086] The recovery module is used to automatically recover the first service instance from failure by restarting; the monitoring module is used to monitor whether the first service instance has recovered from failure after restarting; the sending module is also used to send a third notification message to the monitoring service device to indicate that the first service instance has recovered from failure if the first service instance has recovered from failure after restarting, so that the monitoring service device can send a fourth notification message to the second service instance to indicate that the first service instance has recovered from failure, and the fourth notification message is used to instruct the second service instance to re-establish the dependency relationship with the first service instance.

[0087] In an optional embodiment, the sending module is further configured to: if the first service instance fails to recover after restarting, send a fifth notification message to the monitoring service device indicating that the first service instance has not recovered, so that the monitoring service device can notify the maintenance node to repair the first service instance.

[0088] In one optional embodiment, the server-side device further includes: an analysis module and a determination module;

[0089] The analysis module is used to analyze the working status of the corresponding service instances based on the working status information reported by each service instance; the determination module is used to select the service instance whose working status information indicates a service failure as the first service instance, or to select the service instance that has not reported working status information within a set first time threshold as the first service instance.

[0090] In an optional embodiment, the server device further includes: a reporting module; the reporting module is used to periodically report the working status information of each service instance to the monitoring service device, so that the monitoring service device can monitor whether there is a first server device that has not reported the working status information of multiple service instances within a set second time threshold.

[0091] In an optional embodiment, the sending module is further configured to: if the fault of the first server device is recovered, send a seventh notification message of the fault recovery of the first server device to the monitoring service device, so that the monitoring service device can send an eighth notification message to the third service instance that depends on the service instance on the first server device, the eighth notification message being used to instruct the third service instance to re-establish the dependency relationship with the service instance on the first server device.

[0092] Figure 7 This is a schematic diagram of a monitoring service device provided in an exemplary embodiment of this application. This monitoring service device can be implemented as a monitoring service center in an information processing system, such as... Figure 7 As shown, the monitoring service device includes: a receiving module 71, a determining module 72, and a sending module 73.

[0093] The receiving module 71 is used to receive service dependency information and first notification information reported by each server device in the information processing system between service instances. The first notification information is used to indicate that the first service instance has failed.

[0094] The determination module 72 is used to determine, based on the service dependency information and the first notification information, the second service instance on each server device that has a dependency relationship with the first service instance;

[0095] The sending module 73 is used to send a second notification message to the second service instance to instruct the second service instance to end the dependency relationship between the second service instance and the first service instance.

[0096] In one optional embodiment, the monitoring service device further includes: a monitoring module;

[0097] The receiving module is also used to: receive working status information of multiple service instances sent periodically by each server device;

[0098] The monitoring module is used to monitor whether there is a first server device that has not reported the working status information of multiple service instances within a set second time threshold.

[0099] If present, the determination module is used to determine that the first server device has a service failure, and based on the service dependency information of each service instance, to determine the third service instance that has a dependency relationship with any service instance on the first server device; the sending module is used to send a sixth notification message to the third service instance to instruct the third service instance to end its dependency relationship with the service instance on the first server device.

[0100] In one optional embodiment, the monitoring service device further includes: a notification module;

[0101] The notification module is used to notify the maintenance node to repair the first server device when a service failure is detected.

[0102] In an optional embodiment, the receiving module is further configured to: receive a seventh notification message of first server device fault recovery sent by the first server device;

[0103] The sending module is also configured to: send an eighth notification to the third service instance based on the seventh notification information, instructing the third service instance to re-establish the dependency relationship between itself and the service instance on the first server device.

[0104] The above Figure 5 and Figure 4The communication component is configured to facilitate wired or wireless communication between the device containing the communication component and other devices. The device containing the communication component can access wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G / LTE, 5G, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component also includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID), Infrared Data Association (IrDA) technology, Ultra-Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0105] The above Figure 5 The display includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of the touch or swipe action, but also the duration and pressure associated with the touch or swipe operation.

[0106] The above Figure 5 and Figure 4 The power supply component provides power to the various components of the device in which it resides. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which it resides.

[0107] The above Figure 5 The audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) configured to receive external audio signals when the device containing the audio component is in an operating mode, such as call mode, recording mode, or voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0108] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0109] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0110] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0111] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0112] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0113] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0114] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0115] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0116] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. An information processing method characterized by comprising: The method is suitable for an information processing system, the information processing system comprising at least one server device, each server device being deployed with a plurality of service instances and a target service, the method comprising, for any of the server devices: acquiring, by the target service, service dependency information actively reported by each service instance in the server device and providing the service dependency information to a monitoring service center in the information processing system, the service dependency information representing a calling relationship with other service instances; acquiring, by the target service, working state information reported by each service instance on the server device; when the target service identifies a first service instance having a fault according to the working state information, sending first notification information indicating that the first service instance has a fault to the monitoring service center, so that the monitoring service center determines, according to the service dependency information of each service instance provided by the server device and the first notification information, a second service instance having a dependency relationship with the first service instance on the at least one server device, and sends second notification information to the second service instance to indicate that the second service instance ends the dependency relationship with the first service instance, wherein the target service performs local automatic fault recovery after the first service instance has a fault, and the second service instance re-establishes a dependency relationship with the first service instance after the first service instance is recovered; wherein the target service is further configured to report the working state information of each service instance to the monitoring service center at a regular time, so that the monitoring service center monitors whether there is a first target service that does not report the working state information of a plurality of service instances within a set second time threshold; if there is, it is determined that a service fault occurs in a first server device where the first target service is located; according to the service dependency information of each service instance, a third service instance having a dependency relationship with any service instance on the first server is determined, and sixth notification information is sent to the third service instance to indicate that the third service instance ends the dependency relationship with the service instance on the first server; and a maintenance node is notified to repair the fault of the first server device where the first target service is located.

2. The method of claim 1, wherein, The method further comprises: performing automatic fault recovery on the first service instance in a restart mode, and monitoring whether the first service instance is recovered after being restarted; if the first service instance is recovered after being restarted, third notification information indicating that the first service instance is recovered is sent to the monitoring service center, so that the monitoring service center sends fourth notification information to the second service instance, the fourth notification information being used to indicate that the second service instance re-establishes a dependency relationship with the first service instance.

3. The method of claim 2, wherein, The method further comprises: if the first service instance is not recovered after being restarted, fifth notification information indicating that the first service instance is not recovered is sent to the monitoring service center, so that the monitoring service center notifies a maintenance node to repair the fault of the first service instance.

4. The method of claim 3, wherein, The method further comprises: According to the working state information reported by each service instance, the working state of the corresponding service instance is analyzed; The service instance whose working state information indicates a service failure is taken as the first service instance, or the service instance which has not reported working state information within a set first time threshold is taken as the first service instance.

5. The method of claim 1, wherein, The method further comprises: If the first service end device recovers from the failure, the seventh notification information of the first service end device recovering from the failure is sent to the monitoring service center, so that the monitoring service center sends eighth notification information to a third service instance which depends on the service instance on the first service end device, and the eighth notification information is used to instruct the third service instance to re-establish the dependency relationship between the third service instance and the service instance on the first service end device.

6. An information processing method characterized by comprising: The method is suitable for a monitoring service center in an information processing system, and the method comprises: Receiving service dependency information and first notification information between service instances of a target service in each service end device in the information processing system, the first notification information being used to indicate that a first service instance has failed, and the service dependency information representing a calling relationship with other service instances; According to the service dependency information and the first notification information, a second service instance having a dependency relationship with the first service instance on each service end device is determined, and second notification information is sent to the second service instance to instruct the second service instance to end the dependency relationship with the first service instance, wherein the target service in the service end device performs local automatic failure recovery after the first service instance fails, and the second service instance re-establishes the dependency relationship with the first service instance after the first service instance recovers; Receiving working state information of a plurality of service instances sent by the target service at regular intervals; Monitoring whether there is a first target service which has not reported working state information of the plurality of service instances within a set second time threshold; If there is, it is determined that a service failure occurs in a first service end device where the first target service is located, a third service instance having a dependency relationship with any service instance on the first service end device is determined according to service dependency information of each service instance, and sixth notification information is sent to the third service instance to instruct the third service instance to end the dependency relationship with the service instance on the first service end device; A maintenance node is notified to repair the failure of the first service end device where the first target service is located.

7. The method of claim 6, wherein, The method further comprises: Receiving seventh notification information of the first service end device recovering from the failure sent by the first service end device; According to the seventh notification information, eighth notification information is sent to the third service instance to instruct the third service instance to re-establish the dependency relationship with the service instance on the first service end device.

8. An information processing system, characterized by comprising: Comprise: At least one service end device and a monitoring service center, and each service end device is deployed with a plurality of service instances and a target service; each of the plurality of service instances is configured to actively report working state information to a target service on a service end device where the service instance is located and service dependency information between the service instance and other service instances; the target service is configured to receive the service dependency information reported by each service instance and provide the service dependency information to the monitoring service center, receive the working state information reported by each service instance on the service end device where the target service is located, and when a first service instance that has a fault is identified according to the working state information, send first notification information indicating that the first service instance has a fault to the monitoring service center, and periodically report the working state information of each service instance to the monitoring service center; the monitoring service center is configured to determine a second service instance that has a dependency relationship with the first service instance on the at least one service end device according to the service dependency information of each service instance provided by the target service and the first notification information, and send second notification information to the second service instance to instruct the second service instance to end the dependency relationship with the first service instance, wherein the target service performs local automatic fault recovery after the first service instance has a fault, and the second service instance re-establishes the dependency relationship with the first service instance after the first service instance is recovered; the monitoring service center is further configured to monitor whether there is a first target service that does not report the working state information of a plurality of service instances within a set second time threshold; if there is, determine that a first service end device where the first target service is located has a service fault; determine a third service instance that has a dependency relationship with any service instance on the first service end device according to the service dependency information of each service instance, and send sixth notification information to the third service instance to instruct the third service instance to end the dependency relationship with the service instance on the first service end device; and notify a maintenance node to repair the fault of the first service end device where the first target service is located.

9. The system of claim 8, wherein, the target service is further configured to: perform automatic fault recovery on the first service instance in a restart manner, and monitor whether the first service instance is recovered after being restarted; if the first service instance is recovered after being restarted, send third notification information indicating that the first service instance is recovered to the monitoring service center, so that the monitoring service center sends fourth notification information to the second service instance, the fourth notification information being used to instruct the second service instance to re-establish the dependency relationship with the first service instance.

10. The system of claim 9, wherein, the target service is further configured to: if the first service instance is not recovered after being restarted, send fifth notification information indicating that the first service instance is not recovered to the monitoring service center, so that the monitoring service center notifies a management personnel to repair the fault of the first service instance.

11. The system of claim 8, wherein each service instance is further configured to periodically report the working state information of the service instance to the target service; the target service is further configured to: According to the working state information reported by each service instance, the working state of the corresponding service instance is analyzed; The service instance whose working state information indicates a service failure is taken as the first service instance, or the service instance which does not report the working state information within a set first time threshold is taken as the first service instance.

12. The system of claim 8, wherein, The target service is further configured to: If the first service end device recovers from the failure, the target service sends seventh notification information about the recovery of the first service end device to the monitoring service center; The monitoring service center is further configured to, in a case where the seventh notification information is received, send eighth notification information to the third service instance to instruct the third service instance to re-establish the dependency relationship between the third service instance and the service instance on the first service end device.

13. A server device, comprising: Comprise: The acquisition module, the sending module and the reporting module; The acquisition module is configured to acquire service dependency information actively reported by each service instance in the service end device and provide the service dependency information to a monitoring service device in an information processing system, and acquire working state information reported by each service instance in the service end device, the service dependency information representing a calling relationship with other service instances; The sending module is configured to, when a first service instance having a failure is identified according to the working state information, send first notification information indicating that the first service instance has the failure to the monitoring service device, so that the monitoring service device determines a second service instance having a dependency relationship with the first service instance according to the service dependency information of each service instance provided by the service end device and the first notification information, and sends second notification information to the second service instance to instruct the second service instance to end the dependency relationship with the first service instance, wherein a target service in the service end device performs local automatic failure recovery after the first service instance has the failure, and the second service instance re-establishes the dependency relationship with the first service instance after the first service instance recovers; The reporting module is configured to report the working state information of each service instance to the monitoring service device at a time, so that the monitoring service device monitors whether there is a first service end device which does not report the working state information of multiple service instances within a set second time threshold; if there is, it is determined that the first service end device has a service failure; according to the service dependency information of each service instance, a third service instance having a dependency relationship with any service instance on the first service end device is determined, and sixth notification information is sent to the third service instance to instruct the third service instance to end the dependency relationship with the service instance on the first service end device; and a maintenance node is notified to repair the failure of the first service end device.

14. The apparatus of claim 13, wherein, Further comprise: The recovery module and the monitoring module; The recovery module is configured to automatically recover the first service instance from the failure in a restart mode; The monitoring module is configured to monitor whether the first service instance is recovered after restart; and the sending module is further configured to send, to the monitoring service device, third notification information indicating that the first service instance is recovered after restart, so that the monitoring service device sends fourth notification information indicating that the first service instance is recovered after restart to the second service instance, and the fourth notification information is used to instruct the second service instance to re-establish the dependency relationship between the second service instance and the first service instance.

15. The apparatus of claim 14, wherein, The sending module is further configured to send, to the monitoring service device, fifth notification information indicating that the first service instance is not recovered after restart, so that the monitoring service device notifies a maintenance node to perform fault repair on the first service instance.

16. The apparatus of claim 15, wherein, Further comprising: an analysis module and a determination module; The analysis module is configured to analyze the working state of each service instance according to the working state information reported by each service instance; and the determination module is configured to take a service instance whose working state information indicates a service fault as the first service instance, or take a service instance that does not report working state information within a set first time threshold as the first service instance.

17. The apparatus of claim 13, wherein, The sending module is further configured to send, to the monitoring service device, seventh notification information indicating that the first service instance is recovered after restart, so that the monitoring service device sends eighth notification information to a third service instance that depends on the service instance on the first service instance, and the eighth notification information is used to instruct the third service instance to re-establish the dependency relationship between the third service instance and the service instance on the first service instance.

18. A monitoring service apparatus characterized by comprising: Comprising: a receiving module, a determination module, a monitoring module and a sending module; The receiving module is configured to receive service dependency information and first notification information between service instances of a target service in each service device in an information processing system, the first notification information is used to indicate that a first service instance has a fault, and the service dependency information represents a calling relationship with other service instances; The determination module is configured to determine, according to the service dependency information and the first notification information, a second service instance on each service device that has a dependency relationship with the first service instance; The sending module is configured to send second notification information to the second service instance to instruct the second service instance to end the dependency relationship with the first service instance, wherein the target service in the service device performs local automatic fault recovery after the first service instance has a fault, and the second service instance re-establishes the dependency relationship with the first service instance after the first service instance is recovered; The receiving module is further configured to receive working state information of a plurality of service instances sent by each service device at a time; The monitoring module is configured to monitor, within a set second time threshold, whether there is a first service device that does not report working state information of a plurality of service instances; If the first service end device exists, the determining module is configured to determine that the first service end device has a service failure, and determine, according to service dependency information of each service instance, a third service instance having a dependency relationship with any service instance on the first service end device; and the sending module is configured to send sixth notification information to the third service instance to instruct the third service instance to end the dependency relationship with the service instance on the first service end device.

19. The apparatus of claim 18, wherein, Also comprising: a notification module; the notification module is configured to notify a maintenance node to repair the fault of the first service end device in a case where it is determined that the first service end device has a service failure.

20. The apparatus of claim 19, wherein the receiving module is further configured to receive seventh notification information of the first service end device sent by the first service end device for recovery of the fault of the first service end device; the sending module is further configured to send, according to the seventh notification information, eighth notification information to the third service instance to instruct the third service instance to reestablish the dependency relationship with the service instance on the first service end device.

21. A server device, comprising: comprising: a memory and a processor; the memory is configured to store a computer program; the processor is coupled to the memory and is configured to execute the computer program to implement the information processing method of any one of claims 1-5.

22. A monitoring service device characterized by comprising: a memory and a processor; the memory is configured to store a computer program; and the processor is coupled to the memory and is configured to execute the computer program to implement the information processing method of any one of claims 6-7.

23. A computer readable storage medium storing a computer program, characterized in that, The computer program / instructions, when executed by the processor, implement the steps in the method of any one of claims 1-7.

24. A computer program product comprising computer programs / instructions, characterized in that, The computer program / instructions, when executed by the processor, implement the steps in the method of any one of claims 1-7.

Images