Emergency plan management method and device and electronic equipment

Abstract

The invention provides an emergency plan management method and device and electronic equipment, and the method comprises the steps: receiving a user request, determining a target data center corresponding to the user request, determining whether the target data center is abnormal or not according to a preset evaluation condition, and determining an abnormal process node if the target data center is abnormal, and determining a target exception handling plan corresponding to the abnormal process node from a preset plan data set, and executing the target exception handling plan. According to the embodiment of the invention, when the target data center is abnormal, the pre-compiled exception handling plan with the unified standard is quickly executed, so that the exception existing in the business system can be quickly handled without consuming a large amount of maintenance and cooperation cost, and the use experience of a user is effectively ensured.

Description

Technical Field

[0001] The present application relates to the field of Internet service technology, and in particular to an emergency plan management method, device and electronic equipment. Background Art

[0002] With the rapid development of Internet services, Internet financial business models based on Internet technology and information and communication technology have been widely developed, and the business models have diversified. Among them, Internet financial services have a certain degree of complexity in their service architecture in order to meet the various needs of users, and financial services have their own particularity in providing services. Only efficient and stable financial service capabilities can attract more users.

[0003] When a user requests to use a financial service, a complete service interaction is required to obtain complete financial services, which will generate a very long data service link. This is reflected in: user client -> multiple operator networks -> enterprise data center. After entering the data center, it is reflected in the unified Internet portal -> business application system -> basic services -> third-party institutions.

[0004] In order to provide users with a better user experience, availability must be ensured in every link of business interaction. Usually, multiple teams or systems are responsible for the setting and maintenance of emergency plans for their corresponding links. The inconsistent emergency plan design ideas of each team can easily lead to poor maintainability and high coordination costs in the existing emergency plan management methods. Summary of the invention

[0005] In view of this, the embodiments of the present application provide an emergency plan management method, device and electronic device to unify and standardize the management of various emergency plans, improve the maintainability of the emergency plan management method, and reduce the coordination cost.

[0006] In a first aspect, the present application provides an emergency plan management method, the method comprising:

[0007] Receive a user request, and determine a target data center corresponding to the user request; wherein the target data center is a first production data center and / or a second production data center in the business service system, and the business service system further comprises: a disaster recovery data center, wherein the second production data center is a secondary production data center of the first production data;

[0008] Determine whether the target data center is abnormal according to preset evaluation conditions, and if abnormal, determine the abnormal process node, wherein the process node is each node on the flow link of the flow request in the business service system;

[0009] Determine the target exception handling plan corresponding to the abnormal process node from the preset plan data set, and execute the target exception handling plan, wherein each exception handling plan is pre-written according to preset standard plan writing rules and stored in the exception handling logic file in the preset plan data set.

[0010] In some possible embodiments, the traffic link of the traffic request in the business service system includes: a first traffic link in the first production data center, and a second traffic link in the second production data center, wherein the first traffic link and the second traffic link each include at least the following process nodes: a user entry node, a unified access layer node, each system traffic entry node, each system service module node, and a database system node.

[0011] In some possible embodiments, the preset evaluation condition includes: whether the IP address of the target data center is normal, and the receiving the user request and determining the target data center corresponding to the user request includes:

[0012] Performing domain name resolution on each of the user requests to obtain a number of IP addresses carried in each of the user requests, where each IP address corresponds to a different target data center;

[0013] The determining, according to the preset evaluation condition, whether the target data center is abnormal includes:

[0014] Determine whether the IP address of each target data center is normal;

[0015] If only one production data center has an IP address exception, the abnormal process node is determined to be the user entry node, and a first target exception handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the first target exception handling plan includes:

[0016] The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to another normal production data center, and the normal production data center responds to the user request.

[0017] In some possible embodiments, if the IP address of the first production data center and the IP address of the second production data center are both abnormal, a second target abnormality handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the second target abnormality handling plan includes:

[0018] The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to the disaster recovery data center, and the disaster recovery data center responds to each user request.

[0019] In some possible embodiments, the service instances of each service in the business service system are respectively deployed in their respective corresponding instance groups according to the calling relationship between the upstream and downstream service instances, and the preset evaluation conditions include: whether the calling relationship between the upstream and downstream service instances in each of the instance groups has changed, and determining whether the target data center is abnormal according to the preset evaluation conditions includes:

[0020] If there is a change in the calling relationship between the upstream and downstream service instances, determine that the abnormal process node is a unified access layer node;

[0021] and determining a target instance group in which the calling relationship between the upstream and downstream service instances is changed, and a target service to which the target instance group belongs;

[0022] If the target instance group is only a partial instance group of the target service, a third target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the third target exception handling plan includes:

[0023] Dispatching the user request of the target instance group to other instance groups of the target service except the target instance group, and having the other instance groups respond to the user request;

[0024] Alternatively, if the target instance group is all instance groups of the target service, a fourth target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the fourth target exception handling plan includes:

[0025] A standby instance group of the target service is obtained from the disaster recovery data center, and the standby instance group responds to the user request.

[0026] In some possible embodiments, there is a calling relationship between each system traffic entrance and the business service module in the business service system, and the preset evaluation condition includes: whether the naming rule of the target service received by each system traffic entrance conforms to the preset naming rule, and determining whether the target data center is abnormal according to the preset evaluation condition includes:

[0027] If the naming rule of the target service received by each of the system traffic entrances does not conform to the preset naming rule, determining that the abnormal process node is the system traffic entrance node;

[0028] Determine and execute the fifth target abnormality handling plan corresponding to each system traffic inlet node from the preset plan data set, wherein the fifth target abnormality handling plan includes:

[0029] The name of the target service is modified to a name that complies with the preset naming rule, wherein the preset naming rule includes: the IP address of the target data center+the access port number.

[0030] In some possible embodiments, the first production data center is used to respond to a user's write request, and the second production data center is used to respond to a user's read request. The preset evaluation condition includes: whether a single computer room failure occurs in the first production data center and / or the second production data center. Determining whether the target data center is abnormal according to the preset evaluation condition includes:

[0031] If a single computer room failure occurs in the first production data center and / or the second production data center, a sixth target exception handling plan corresponding to the database system node is determined from the preset plan data set and executed, and the sixth target exception handling plan includes:

[0032] If a single computer room failure occurs in the first production data center and / or the second production data center, the target database proxy is used to migrate user requests on the computer room where the single computer room failure occurred to a computer room where the single computer room failure has not occurred, wherein the target database proxy is a data proxy for stateless services.

[0033] In some possible embodiments, the method further includes:

[0034] For each of the process nodes, a process entity is generated based on preset domain name resolution rules, inlet traffic scheduling rules, service discovery rules and custom plan execution logic, wherein the custom plan execution logic is the execution logic pre-written by each development team based on the standard plan writing rules;

[0035] Generate the same plan label for the process entities corresponding to the same process nodes in the first production data center and the second production data center;

[0036] The step of determining the target exception handling plan corresponding to the abnormal process node from the preset plan data set includes:

[0037] According to the target plan label corresponding to the abnormal process node, the target process entity corresponding to the target plan label is determined from the preset plan data set.

[0038] In some possible embodiments, the method further includes:

[0039] If the abnormal production data center returns to normal, stop executing the target abnormality handling plan.

[0040] In a second aspect, the present application provides an emergency plan management device, the device comprising:

[0041] A user request receiving module is used to receive a user request and determine a target data center corresponding to the user request; wherein the target data center is a first production data center and / or a second production data center in the business service system, and the business service system further includes: a disaster recovery data center, wherein the second production data center is a secondary production data center of the first production data;

[0042] A determination module, used to determine whether the target data center is abnormal according to a preset evaluation condition, and if abnormal, determine the abnormal process node, wherein the process node is each node on the flow link of the flow request in the business service system;

[0043] The plan execution module is used to determine the target exception handling plan corresponding to the abnormal process node from the preset plan data set and execute the target exception handling plan, wherein each exception handling plan is pre-written according to the preset standard plan writing rules and stored in the exception handling logic file in the preset plan data set.

[0044] In some possible embodiments, the traffic link of the traffic request in the business service system includes: a first traffic link in the first production data center, and a second traffic link in the second production data center, wherein the first traffic link and the second traffic link each include at least the following process nodes: a user entry node, a unified access layer node, each system traffic entry node, each system service module node, and a database system node.

[0045] In some possible embodiments, the preset evaluation condition includes: whether the IP address of the target data center is normal, and the plan execution module is specifically used to:

[0046] Performing domain name resolution on each of the user requests to obtain a number of IP addresses carried in each of the user requests, where each IP address corresponds to a different target data center;

[0047] The determining, according to the preset evaluation condition, whether the target data center is abnormal includes:

[0048] Determine whether the IP address of each target data center is normal;

[0049] If only one production data center has an IP address exception, the abnormal process node is determined to be the user entry node, and a first target exception handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the first target exception handling plan includes:

[0050] The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to another normal production data center, and the normal production data center responds to the user request.

[0051] In some possible embodiments, if the IP address of the first production data center and the IP address of the second production data center are both abnormal, a second target abnormality handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the second target abnormality handling plan includes:

[0052] The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to the disaster recovery data center, and the disaster recovery data center responds to each user request.

[0053] In some possible embodiments, the service instances of each service in the business service system are respectively deployed in their corresponding instance groups according to the calling relationship between the upstream and downstream service instances, and the preset evaluation conditions include: whether the calling relationship between the upstream and downstream service instances in each of the instance groups has changed, and the plan execution module is specifically used to:

[0054] If there is a change in the calling relationship between the upstream and downstream service instances, determine that the abnormal process node is a unified access layer node;

[0055] and determining a target instance group in which the calling relationship between the upstream and downstream service instances is changed, and a target service to which the target instance group belongs;

[0056] If the target instance group is only a partial instance group of the target service, a third target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the third target exception handling plan includes:

[0057] Dispatching the user request of the target instance group to other instance groups of the target service except the target instance group, and having the other instance groups respond to the user request;

[0058] Alternatively, if the target instance group is all instance groups of the target service, a fourth target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the fourth target exception handling plan includes:

[0059] A standby instance group of the target service is obtained from the disaster recovery data center, and the standby instance group responds to the user request.

[0060] In some possible embodiments, there is a calling relationship between each system traffic entrance and the business service module in the business service system, and the preset evaluation condition includes: whether the naming rule of the target service received by each system traffic entrance conforms to the preset naming rule, and the plan execution module is specifically used to:

[0061] If the naming rule of the target service received by each of the system traffic entrances does not conform to the preset naming rule, determining that the abnormal process node is the system traffic entrance node;

[0062] Determine and execute the fifth target abnormality handling plan corresponding to each system traffic inlet node from the preset plan data set, wherein the fifth target abnormality handling plan includes:

[0063] The name of the target service is modified to a name that complies with the preset naming rule, wherein the preset naming rule includes: the IP address of the target data center+the access port number.

[0064] In some possible embodiments, the first production data center is used to respond to a user's write request, and the second production data center is used to respond to a user's read request. The preset evaluation condition includes: whether a single computer room failure occurs in the first production data center and / or the second production data center. The plan execution module is specifically used to:

[0065] If a single computer room failure occurs in the first production data center and / or the second production data center, a sixth target exception handling plan corresponding to the database system node is determined from the preset plan data set and executed, and the sixth target exception handling plan includes:

[0066] If a single computer room failure occurs in the first production data center and / or the second production data center, the target database proxy is used to migrate user requests on the computer room where the single computer room failure occurred to a computer room where the single computer room failure has not occurred, wherein the target database proxy is a data proxy for stateless services.

[0067] In some possible embodiments, the device further includes:

[0068] An entity generation module, for generating a process entity for each of the process nodes based on preset domain name resolution rules, inlet traffic scheduling rules, service discovery rules, and custom plan execution logic, wherein the custom plan execution logic is the execution logic pre-written by each development team based on the standard plan writing rules;

[0069] Generate the same plan label for the process entities corresponding to the same process nodes in the first production data center and the second production data center;

[0070] The plan execution module is specifically used for:

[0071] According to the target plan label corresponding to the abnormal process node, the target process entity corresponding to the target plan label is determined from the preset plan data set.

[0072] In some possible embodiments, the plan execution module is further used to:

[0073] If the abnormal production data center returns to normal, stop executing the target abnormality handling plan.

[0074] In a third aspect, the present application provides an electronic device, the electronic device comprising:

[0075] a processor; and a memory storing a program,

[0076] The program includes instructions, which, when executed by the processor, enable the processor to execute the emergency plan management method according to the first aspect.

[0077] In a fourth aspect, the present application provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the emergency plan management method according to the first aspect.

[0078] Beneficial effects of this application:

[0079] The present application provides an emergency plan management method, device and electronic device, wherein the method receives a user request, determines a target data center corresponding to the user request, and determines whether the target data center is abnormal based on preset evaluation conditions. If abnormal, the abnormal process node is determined, and a target exception handling plan corresponding to the abnormal process node is determined from a preset plan data set, and the target exception handling plan is executed.

[0080] The embodiment of the present application is selected to subdivide the business service system into the first production data center, the second production data center and the disaster recovery data center, wherein the second production data center is a slave data center of the first production data center, and the data center is logically divided into various process nodes by pre-setting the nodes on the traffic link in the business service system according to the traffic request, and then the development team of each process node writes the exception handling plan corresponding to each process node according to the preset standard plan writing rules. In this way, when an exception occurs in the target data center, the pre-written unified standard exception handling plan is quickly executed, so that the exceptions in the business system can be quickly handled without consuming a lot of maintenance and coordination costs, effectively ensuring the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] Further details, features and advantages of the present application are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:

[0082] Figure 1 A schematic diagram of a process flow of an emergency plan management method provided by an embodiment of the present application is shown;

[0083] Figure 2 A schematic diagram of a system architecture of a business service system provided by an embodiment of the present application is shown;

[0084] Figure 3 A schematic diagram of a process for generating an exception handling plan provided in an embodiment of the present application is shown;

[0085] Figure 4 A logical structure diagram of an emergency plan management device provided in an embodiment of the present application is shown;

[0086] Figure 5 A schematic diagram of a logical structure of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0087] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as being limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not intended to limit the scope of protection of the present application.

[0088] It should be understood that the various steps described in the method implementation of the present application can be performed in different orders and / or performed in parallel. In addition, the method implementation may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this respect.

[0089] The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below. It should be noted that the concepts of "first", "second", etc. mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0090] It should be noted that the modifications of "one" and "plurality" mentioned in the present application are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0091] As described in the background technology, the existing emergency plan management method relies on multiple teams and multiple systems for maintenance. Under normal circumstances, the emergency plan response can be carried out normally. However, considering the rapid iteration of business modules, version upgrades of system architecture, changes in the underlying environment, etc., the existing emergency plan management method is prone to the following disadvantages:

[0092] Disadvantage 1: Poor maintainability. This is mainly reflected in the fact that different teams and systems have different design ideas for the plan, and it is difficult to maintain the effectiveness of the relevant plan during the system iteration process.

[0093] Disadvantage 2: The cost of plan rehearsal and verification is high. Since the design and maintenance methods of each system source are different, the corresponding plan rehearsal work requires the maintenance personnel of each system to conduct the rehearsal together. The execution capabilities of each plan are different, the rehearsal cost is high, and it is difficult for each team to verify the effectiveness of the plan at the same time.

[0094] Disadvantage 3: High collaborative execution cost. Once a fault actually occurs, the execution timeliness of the system sources maintained by each team will be greatly reduced, resulting in low efficiency in stopping the fault, further causing operational losses and affecting user experience.

[0095] In view of this, the present application provides an emergency plan management method, device and electronic device, wherein the emergency plan management method is applied to any electronic device with emergency plan management capabilities, including but not limited to personal mobile terminals, computer equipment, servers, etc.

[0096] In the first aspect, the present application provides an emergency plan management method, such as Figure 1 As shown, the method comprises the following steps:

[0097] S11. Receive a user request and determine a target data center corresponding to the user request.

[0098] Among them, the target data center is the first production data center and / or the second production data center in the business service system, and the business service system also includes: a disaster recovery data center, wherein the second production data center is a secondary production data center of the first production data.

[0099] S12. Determine whether the target data center is abnormal according to preset evaluation conditions, and if abnormal, determine the abnormal process node.

[0100] The process nodes are nodes on the flow link of the flow request in the business service system;

[0101] S13: Determine the target exception handling plan corresponding to the abnormal process node from the preset plan data set, and execute the target exception handling plan.

[0102] Among them, each exception handling plan is pre-written according to preset standard plan writing rules and is stored in the exception handling logic file in the preset plan data set.

[0103] The embodiment of the present application is selected to subdivide the business service system into the first production data center, the second production data center and the disaster recovery data center, wherein the second production data center is a slave data center of the first production data center, and the data center is logically divided into various process nodes by pre-setting the nodes on the traffic link in the business service system according to the traffic request, and then the development team responsible for each process node writes the exception handling plan corresponding to each process node according to the preset standard plan writing rules. In this way, when an exception occurs in the target data center, the pre-written unified standard exception handling plan is quickly executed, so that the exceptions in the business system can be quickly handled without consuming a lot of maintenance and coordination costs, effectively ensuring the user experience.

[0104] The above steps S11 to S13 are described in detail below:

[0105] In the embodiments of the present application, the business service system refers to various platforms or software systems that provide Internet business services based on Internet technology. For example, taking the Internet business as financial credit business, the business service system may refer to an Internet financial credit business platform or an Internet financial credit business system, through which business services such as loan application, loan repayment, and credit limit approval can be provided to users.

[0106] In the embodiment of the present application, a user request refers to a request from a user to obtain a service from a business service system, and specifically refers to a data request initiated by a user terminal device to a device of the business service system, including a data read request and a data write request. In the embodiment of the present application, such data requests initiated by users are collectively referred to as traffic. The emergency plan management method provided in the embodiment of the present application is actually to manage the exception handling plan. The exception handling plan is essentially a traffic scheduling method when the business service system is abnormal. It flexibly schedules user traffic to ensure that the user request is responded to without the user being aware of the abnormality, so as to ensure the user experience.

[0107] Based on this, in some embodiments, the emergency plan management method provided by the present application is applied to the business service system to manage the exception handling plans on each process node in the business service system, and when the business service system fails, quickly determine the corresponding exception handling plan to schedule and respond to user traffic, and maintain the abnormal data center, computer room, service instance, etc. in combination with the fault maintenance strategy of the data center. In some embodiments, the system framework structure of the business service system can be as follows: Figure 2 As shown, it includes the following parts:

[0108] The first production data center, the second production data center, and the disaster recovery data center. Among them, the second production data center is a slave data center of the first production data center, which is used to back up the data in the first production data center, and respond to the data request originally sent to the first data center when the entire data center of the first production data center fails. The disaster recovery data center can be regarded as a data center set up to deal with extreme failure situations. It is a static data center that does not receive user requests under normal circumstances. It only receives user requests when both the first production data center and the second production data center fail, and only undertakes the most core business traffic. The specific description of the disaster recovery data center can refer to the relevant patent documents of the applicant's disaster recovery data center, and this application will not repeat it.

[0109] In the embodiment of the present application, each data center is the implementation basis of the business service system and the back-end database of the business service system. The Internet business services provided by the business service system are all implemented based on the data stored in the data center. Therefore, the stability of the data center determines the stability of the business service system, and even more so determines the user experience of the business service system. In the embodiment of the present application, the first production data center and the second production data center constitute a "dual-active data center" architecture. During the normal provision of business services by the business service system, the first production data center and the second production data center are both in a state of normal operation, and the second production data center is a slave data center of the first production data center. In other words, the data stored in the second production data center is a backup of the data stored in the first production data center, and the data stored in the two data centers are the same.

[0110] Therefore, in order to ensure data consistency, the databases of the two data centers adopt a master-slave architecture, read-write separation, or use distributed storage technology to establish a multi-copy model to achieve data consistency between the two. In some possible embodiments, the first production data center is used to respond to user write requests, and the second production data center is used to respond to user read requests.

[0111] In the embodiment of the present application, the preset evaluation conditions are business system status evaluation conditions set in advance by business system maintenance personnel based on historical maintenance records, which can be further subdivided into evaluation conditions for data centers, evaluation conditions for computer rooms in data centers, evaluation conditions for services deployed in computer rooms, evaluation conditions for process nodes, and so on. Specific evaluation conditions can be flexibly set according to actual needs, and this application does not strictly limit them. As an example, taking the evaluation conditions of a data center as an example, the preset evaluation conditions include: whether the IP address of the data center is normal. If it is normal, it indicates that the data center is operating normally and can receive or send data normally. If the IP address is abnormal, it indicates that the data center cannot send or receive data normally.

[0112] Based on this, when executing step S12, the target data center can be evaluated in multiple dimensions according to different preset evaluation conditions to determine whether all links and modules of the target data center are operating normally. As an implementation method, each process node of the target data center can be evaluated according to the preset evaluation conditions of each process node to determine whether each process node is normal. If one of the process nodes does not meet the corresponding preset evaluation conditions, it can be determined that the target data center is abnormal. At this time, the process node that does not meet the preset evaluation conditions is determined as an abnormal process node.

[0113] In the embodiment of the present application, the process node refers to each node on the traffic link of the traffic request in the business service system. The specific number of nodes on the traffic link and the division position can be flexibly set by the business developer according to actual needs, and this application does not strictly limit it. The traffic link of the traffic request in the business service system includes: a first traffic link in the first production data center and a second traffic link in the second production data center. As a preferred implementation, it can be as follows Figure 2 As shown, the first traffic link and the second traffic link both include at least the following process nodes: user entry node, unified access layer node, each system traffic entry node, each system service module node, and database system node.

[0114] As mentioned above, the user's request is essentially a traffic request. In an embodiment of the present application, in order to facilitate the management of the plan team and save collaboration costs, the present application subdivides the traffic links of the traffic requests in the data center and divides them according to process nodes, so that different developers or teams and systems are responsible for the maintenance of the corresponding process nodes, further improving the completeness of the business service system functions and the response efficiency.

[0115] Among them, each developer or team, system is responsible for the preparation of the exception handling plan for the corresponding process node. In an embodiment of the present application, the exception handling plan refers to the exception handling logic file that is pre-prepared by the developer corresponding to each process node in accordance with the preset standard plan writing rules and stored in the preset plan data set. Among them, the preset standard plan writing rules stipulate the domain name resolution rules, traffic scheduling rules and specific operating logic of the name discovery service module of each process node. The specific operating logic includes data transmission interface, data verification, etc. Developers, teams or systems can write corresponding traffic scheduling plans based on this set of standard plan writing rules, combined with various types of faults that are prone to occur in their own process nodes.

[0116] Among them, the preset plan data set can be regarded as a plan database, and the corresponding target exception handling plan can be obtained by calling the plan database. As an implementation method, each exception handling plan includes label information, and the label information is used to identify the process node corresponding to the exception handling plan. In this way, when executing the above step S13, the corresponding target exception handling plan can be obtained from the plan database according to the label information corresponding to the process node.

[0117] It can be seen that the exception handling plan is subdivided according to the process node, and different process nodes correspond to different exception handling plans. As an implementation method, the exception handling plan can be regarded as a process entity. As an example, Figure 3 As shown, the process entity is obtained in advance in the following way:

[0118] For each of the process nodes, a process entity is generated based on preset domain name resolution rules, inlet traffic scheduling rules, service discovery rules and custom plan execution logic, wherein the custom plan execution logic is the execution logic pre-written by each development team based on the standard plan writing rules;

[0119] Generate the same plan label for the process entities corresponding to the same process nodes in the first production data center and the second production data center;

[0120] The step of determining the target exception handling plan corresponding to the abnormal process node from the preset plan data set includes:

[0121] According to the target plan label corresponding to the abnormal process node, the target process entity corresponding to the target plan label is determined from the preset plan data set.

[0122] In the embodiments of the present application, an entity is an abstract logical concept, which is essentially a computer program logic. Each development team writes the execution logic in advance based on the standard plan writing rules. For example, the development team writes the methods, interfaces, data, etc. required for scheduling in the event of an abnormality based on the standard plan writing requirements according to the abnormal situations that are prone to occur in the daily process nodes that they are responsible for, and obtains a complete set of exception handling plan execution logic. This execution logic can be directly triggered according to the preset evaluation conditions during the operation of the program language, and then the computer room, database system or service instance in the data center is targeted for fault handling. In other words, when each development team writes the execution logic of the exception handling plan, it must use the same standard plan writing rules as other development teams. This is the basis for ensuring that the method provided in the embodiments of the present application can be executed normally. For example, the unified access layer serves as a unified management system for traffic entrances. Under normal circumstances, both data centers accept traffic. For each service cluster, each data center has a sub-cluster, which can forward business traffic to back-end services according to configuration rules. By default, the sub-cluster forwards 100% of the traffic to the back-end of the same data center. The plan is to define the traffic mapping method of each cluster as an entity object, configure the traffic scheduling logic in advance, and quickly execute stop-loss in abnormal scenarios of a single data center.

[0123] Among them, for the process entities corresponding to the same process nodes in the first production data center and the second production data center, such as the same unified access layer node, the same "unified access layer" label is generated. When an abnormality occurs in the unified access layer node, the abnormality handling plan corresponding to the unified access layer nodes of the first production data center and the second production data center can be directly obtained based on the "unified access layer" label, and then it can be determined whether the unified access layer node in the first production data center or the unified access layer node in the second production data center is abnormal, and the traffic at the unified access layer node is scheduled in a targeted manner.

[0124] As an implementation method, different labels can be set according to different fault scenarios, so that in the corresponding fault scenario, the corresponding target exception handling plan can be quickly and automatically found and executed based on the fault type. The embodiment of the present application is selected to generate process entities by generating process entities according to the preset domain name resolution rules, inlet traffic scheduling rules, service discovery rules and custom plan execution logic for the exception handling plans of different process nodes, and adding plan labels of the plan group to which they belong to the process entities under different process nodes. In this way, the exception handling plan can be automatically executed, making the failure loss prevention efficiency faster.

[0125] In some possible embodiments, based on the above steps S11 to S13, the method further includes:

[0126] If the abnormal production data center returns to normal, stop executing the target abnormality handling plan.

[0127] This step is equivalent to re-executing step S12, and performing a second evaluation on the production data center according to the preset evaluation conditions. If the abnormal production data center resumes normal operation, the traffic that was abnormally migrated to other data centers, or other computer rooms or other server devices due to the abnormal production data center can be migrated back to the restored normal production data center, so as to achieve abnormal maintenance without the user noticing and effectively protect the user experience.

[0128] As described above, different process nodes correspond to different preset evaluation conditions. In some possible embodiments, for a user entry node, the preset evaluation condition includes: whether the IP address of the target data center is normal, and the receiving of a user request and determining the target data center corresponding to the user request includes:

[0129] Performing domain name resolution on each of the user requests to obtain a number of IP addresses carried in each of the user requests, where each IP address corresponds to a different target data center;

[0130] The determining, according to the preset evaluation condition, whether the target data center is abnormal includes:

[0131] Determine whether the IP address of each target data center is normal;

[0132] If only one production data center has an IP address exception, the abnormal process node is determined to be the user entry node, and a first target exception handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the first target exception handling plan includes:

[0133] The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to another normal production data center, and the normal production data center responds to the user request.

[0134] Alternatively, if both the IP address of the first production data center and the IP address of the second production data center are abnormal, a second target abnormality handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the second target abnormality handling plan includes:

[0135] The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to the disaster recovery data center, and the disaster recovery data center responds to each user request.

[0136] Specifically, the domain name resolution result of the business service system will be multiple IP addresses, and each IP address corresponds to its own data center. The IP address resolved under normal circumstances (that is, when the data center is in a normal state) will only be the IP address of the production data center, such as how many IPV4 (Internet Protocol version 4) and IPV6 (Internet Protocol version 6) results are included. If a single data center is abnormal, the IP address of the abnormal data center will not be able to communicate normally, or there will be no data transmission. At this time, it is necessary to distinguish between two situations: whether only one production data center is abnormal, or both production data centers are abnormal. In the case where only one production data center is abnormal, user requests of the abnormal production data center are migrated to another normal production data center. During the process, the IP address of the abnormal data center needs to be blocked to prevent users from continuing to send requests to the abnormal data center, thereby achieving the effect of rapid fault isolation.

[0137] For example, if the second production data center is abnormal, the destination IP address of the user request accessing the second production data center will be changed to the first production data center, thereby realizing the migration of user requests. In the case where both production data centers are abnormal, the probability of this happening is extremely low. At this time, the disaster recovery data center is enabled, the IP address of the disaster recovery data center is resolved, and the resolution result of the production data center is blocked, and the traffic is introduced to the disaster recovery data center.

[0138] In some possible embodiments, the service instances of each service in the business service system, especially in the unified access layer node, are respectively deployed in their corresponding instance groups according to the call relationship between the upstream and downstream service instances. Therefore, for the unified access layer node, the preset evaluation condition includes: whether the call relationship between the upstream and downstream service instances in each instance group has changed, and the determination of whether the target data center is abnormal according to the preset evaluation condition includes:

[0139] If there is a change in the calling relationship between the upstream and downstream service instances, determine that the abnormal process node is a unified access layer node;

[0140] and determining a target instance group in which the calling relationship between the upstream and downstream service instances is changed, and a target service to which the target instance group belongs;

[0141] If the target instance group is only a partial instance group of the target service, a third target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the third target exception handling plan includes:

[0142] Dispatching the user request of the target instance group to other instance groups of the target service except the target instance group, and having the other instance groups respond to the user request;

[0143] Alternatively, if the target instance group is all instance groups of the target service, a fourth target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the fourth target exception handling plan includes:

[0144] A standby instance group of the target service is obtained from the disaster recovery data center, and the standby instance group responds to the user request.

[0145] Under normal conditions, various business services are deployed in the data center, such as credit application services, credit review services, etc. Usually, various business services are implemented by various service instances. Service instances refer to: the smallest unit of service deployment. Generally, services are distributed and deployed in the data center. Multiple instances that provide the same function constitute a service. For example, the credit application service is divided into several service instances and distributed and deployed in the data center. Each service instance calls each other to jointly provide the Internet service of credit application. In the embodiment of the present application, Internet service refers to a functional unit that runs independently according to the system design and can provide API interface logic to the outside world.

[0146] Under normal circumstances, the upstream service instance calls the downstream service instance, and the service instances of each service are deployed in their respective corresponding instance groups according to the calling relationship between the upstream and downstream service instances, wherein the calling relationship between the upstream and downstream services is determined based on the mutual calling between the service instances. This deployment method has a short physical distance between the service instances in the same instance group, and the calling delay is low, which helps to ensure the stability of the business service system. For example, taking the service instance of the credit application service as an example, it is assumed that it includes service instance A, service instance B, and service instance C. The calling relationship between the three service instances is that service instance A calls service instance B, and service instance B calls service instance C. At this time, service instance A is the upstream service instance of service instance B, service instance A and service instance B are the upstream service instances of service instance C, and service instance B and service instance C are the downstream service instances of service instance A. According to this upstream and downstream service instance calling relationship, service instance A, service instance B, and service instance C of the credit application service are deployed in a service instance group.

[0147] In order to ensure the normal operation of the service, the calling relationship between the upstream and downstream service instances usually does not change. It will only change when the system is upgraded or the service is upgraded. At this time, the calling relationship between the upstream and downstream service instances originally written in the unified access layer node will not be reused. At this time, the unified access layer node will be abnormal. Based on this, the preset evaluation conditions may include: whether the calling relationship between the upstream and downstream service instances in each of the instance groups has changed. If a change occurs, first determine the target instance group that has changed. If it is only a part of the instance group, the user request of the abnormal target instance group is dispatched to other instance groups of the target service except the target instance group, and the other instance groups respond to the user request. The other instance groups must be instance groups whose calling relationship has not changed. In this way, the normal operation of other instance groups to return data to the user request helps to change the service group providing the service without the user noticing. And the target instance group can be isolated to avoid larger failures.

[0148] A special case is that the calling relationships between all service instances of the target service have changed. This is an extreme case. For example, the calling relationships between all service instances of the credit application service have changed. At this time, the backup instance group of the target service will be obtained from the disaster recovery data center, and the backup instance group will respond to user requests and return service data to the user.

[0149] In some possible embodiments, in the business service system, especially in each system traffic entry node, there is a call relationship between each system traffic entry and a business service module, and the preset evaluation condition includes: whether the naming rule of the target service received by each system traffic entry conforms to the preset naming rule, and determining whether the target data center is abnormal according to the preset evaluation condition includes:

[0150] If the naming rule of the target service received by each of the system traffic entrances does not conform to the preset naming rule, determining that the abnormal process node is the system traffic entrance node;

[0151] Determine and execute the fifth target abnormality handling plan corresponding to each system traffic inlet node from the preset plan data set, wherein the fifth target abnormality handling plan includes:

[0152] The name of the target service is modified to a name that complies with the preset naming rule, wherein the preset naming rule includes: the IP address of the target data center+the access port number.

[0153] In the embodiment of the present application, the service management of the data center is implemented based on the name service function module in the business service system, that is, all services are managed based on the name of the service. The name discovery module can determine the type of service provided based on the name of the service, so in order to ensure the accurate data forwarding of each service, the naming of each service needs to comply with the preset naming rules, such as the form of the IP address + access port number of the target data center. In this way, when the naming of the target service does not comply with the preset naming rules, the data support cannot be provided by using the data corresponding to the target service in the back-end database. At this time, the name of the target service needs to be changed to a name that complies with the unified naming rules. In this way, the deployment location of the service instance providing the target service can be quickly determined based on the IP address and access port number in the name.

[0154] By selecting the embodiment of the present application, each service can be deployed and isolated through the service naming rules, further realizing the isolation of business access traffic room, which is conducive to the subsequent direct traffic scheduling based on the service name.

[0155] As mentioned above and Figure 2 In the related description, the first production data center is used to respond to the user's write request, and the second production data center is used to respond to the user's read request. Based on this, in some embodiments, the preset evaluation condition in step S12 may also include: whether a single machine room failure occurs in the first production data center and / or the second production data center, and the determination of whether the target data center is abnormal according to the preset evaluation condition includes:

[0156] If a single computer room failure occurs in the first production data center and / or the second production data center, a sixth target exception handling plan corresponding to the database system node is determined from the preset plan data set and executed, and the sixth target exception handling plan includes:

[0157] If a single computer room failure occurs in the first production data center and / or the second production data center, the target database proxy is used to migrate user requests on the computer room where the single computer room failure occurred to a computer room where the single computer room failure has not occurred, wherein the target database proxy is a data proxy for stateless services.

[0158] As an implementation method, since the first production data center and the second production data center are in real-time operation, it is impossible to make the data stored or the service instances deployed on the two data centers completely identical. Therefore, there can only be one computer room in the first production data center. Through the designed read-write isolation solution (i.e., the first production data center is responsible for receiving the user's write request, and the second production data center is responsible for receiving the user's read request), a stateless service processing capability is provided by means of SQL (Structured Query Language) proxy, that is, the SQL agent in the data center can process the user's request without relying on any previous request information or status. In this way, traffic isolation on database systems, distribution of SQL commands by SQL agents, and master-slave switching between databases with network anomalies, etc. can be achieved, which can be scheduled with the help of this stateless service processing capability. When a single computer room fails, master-slave switching can be quickly achieved, which effectively improves the loss-stopping capability of the database during failures and effectively reduces losses.

[0159] Among them, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in this application are in compliance with the relevant laws and regulations and do not violate public order and good morals.

[0160] In a second aspect, the present application embodiment provides an emergency plan management device, such as Figure 4 As shown, the device 40 includes:

[0161] The user request receiving module 401 is used to receive a user request and determine a target data center corresponding to the user request; wherein the target data center is a first production data center and / or a second production data center in the business service system, and the business service system further includes: a disaster recovery data center, wherein the second production data center is a secondary production data center of the first production data;

[0162] The determination module 402 is used to determine whether the target data center is abnormal according to a preset evaluation condition, and if abnormal, determine the abnormal process node, wherein the process node is each node on the flow link of the flow request in the business service system;

[0163] The plan execution module 403 is used to determine the target exception handling plan corresponding to the abnormal process node from the preset plan data set, and execute the target exception handling plan, wherein each exception handling plan is pre-written according to preset standard plan writing rules and stored in the exception handling logic file in the preset plan data set.

[0164] In some possible embodiments, the traffic link of the traffic request in the business service system includes: a first traffic link in the first production data center, and a second traffic link in the second production data center, wherein the first traffic link and the second traffic link each include at least the following process nodes: a user entry node, a unified access layer node, each system traffic entry node, each system service module node, and a database system node.

[0165] In some possible embodiments, the preset evaluation condition includes: whether the IP address of the target data center is normal, and the plan execution module is specifically used to:

[0166] Performing domain name resolution on each of the user requests to obtain a number of IP addresses carried in each of the user requests, where each IP address corresponds to a different target data center;

[0167] The determining, according to the preset evaluation condition, whether the target data center is abnormal includes:

[0168] Determine whether the IP address of each target data center is normal;

[0169] If only one production data center has an IP address exception, the abnormal process node is determined to be the user entry node, and a first target exception handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the first target exception handling plan includes:

[0170] The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to another normal production data center, and the normal production data center responds to the user request.

[0171] Alternatively, if both the IP address of the first production data center and the IP address of the second production data center are abnormal, a second target abnormality handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the second target abnormality handling plan includes:

[0172] The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to the disaster recovery data center, and the disaster recovery data center responds to each user request.

[0173] In some possible embodiments, the service instances of each service in the business service system are respectively deployed in their corresponding instance groups according to the calling relationship between the upstream and downstream service instances, and the preset evaluation conditions include: whether the calling relationship between the upstream and downstream service instances in each of the instance groups has changed, and the plan execution module is specifically used to:

[0174] If there is a change in the calling relationship between the upstream and downstream service instances, determine that the abnormal process node is a unified access layer node;

[0175] and determining a target instance group in which the calling relationship between the upstream and downstream service instances is changed, and a target service to which the target instance group belongs;

[0176] If the target instance group is only a partial instance group of the target service, a third target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the third target exception handling plan includes:

[0177] Dispatching the user request of the target instance group to other instance groups of the target service except the target instance group, and having the other instance groups respond to the user request;

[0178] Alternatively, if the target instance group is all instance groups of the target service, a fourth target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the fourth target exception handling plan includes:

[0179] A standby instance group of the target service is obtained from the disaster recovery data center, and the standby instance group responds to the user request.

[0180] In some possible embodiments, there is a calling relationship between each system traffic entrance and the business service module in the business service system, and the preset evaluation condition includes: whether the naming rule of the target service received by each system traffic entrance conforms to the preset naming rule, and the plan execution module is specifically used to:

[0181] If the naming rule of the target service received by each of the system traffic entrances does not conform to the preset naming rule, determining that the abnormal process node is the system traffic entrance node;

[0182] Determine and execute the fifth target abnormality handling plan corresponding to each system traffic inlet node from the preset plan data set, wherein the fifth target abnormality handling plan includes:

[0183] The name of the target service is modified to a name that complies with the preset naming rule, wherein the preset naming rule includes: the IP address of the target data center+the access port number.

[0184] In some possible embodiments, the first production data center is used to respond to a user's write request, and the second production data center is used to respond to a user's read request. The preset evaluation condition includes: whether a single computer room failure occurs in the first production data center and / or the second production data center. The plan execution module is specifically used to:

[0185] If a single computer room failure occurs in the first production data center and / or the second production data center, a sixth target exception handling plan corresponding to the database system node is determined from the preset plan data set and executed, and the sixth target exception handling plan includes:

[0186] If a single computer room failure occurs in the first production data center and / or the second production data center, the target database proxy is used to migrate user requests on the computer room where the single computer room failure occurred to a computer room where the single computer room failure has not occurred, wherein the target database proxy is a data proxy for stateless services.

[0187] In some possible embodiments, the device further includes:

[0188] An entity generation module, for generating a process entity for each of the process nodes based on preset domain name resolution rules, inlet traffic scheduling rules, service discovery rules, and custom plan execution logic, wherein the custom plan execution logic is the execution logic pre-written by each development team based on the standard plan writing rules;

[0189] Generate the same plan label for the process entities corresponding to the same process nodes in the first production data center and the second production data center;

[0190] The plan execution module is specifically used for:

[0191] According to the target plan label corresponding to the abnormal process node, the target process entity corresponding to the target plan label is determined from the preset plan data set.

[0192] In some possible embodiments, the plan execution module is further used to:

[0193] If the abnormal production data center returns to normal, stop executing the target abnormality handling plan.

[0194] The names of the messages or information exchanged between multiple devices in the embodiments of the present application are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0195] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: at least one processor; and a memory connected to the at least one processor in communication. The memory stores a computer program that can be executed by the at least one processor, and when the computer program is executed by the at least one processor, the electronic device performs a method according to an embodiment of the present application.

[0196] In a fourth aspect, an embodiment of the present application further provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to perform a method according to an embodiment of the present application.

[0197] In a fifth aspect, an embodiment of the present application further provides a computer program product, comprising a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to perform a method according to an embodiment of the present application.

[0198] refer to Figure 5 , the structural block diagram of the electronic device 500 that can be used as the server or client of the present application will now be described, which is an example of hardware devices that can be applied to various aspects of the present application. The electronic device is intended to represent various forms of digital electronic computer equipment, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are only examples, and are not intended to limit the implementation of the present application described and / or required herein.

[0199] like Figure 5 As shown, the electronic device 500 includes a computing unit 501, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 502 or a computer program loaded from a storage unit 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 can also be stored. The computing unit 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0200] A plurality of components in the electronic device 500 are connected to the I / O interface 505, including: an input unit 506, an output unit 507, a storage unit 508, and a communication unit 509. The input unit 506 may be any type of device capable of inputting information to the electronic device 500, and the input unit 506 may receive input digital or character information, and generate key signal inputs related to user settings and / or function control of the electronic device. The output unit 507 may be any type of device capable of presenting information, and may include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 508 may include, but is not limited to, a disk, an optical disk. The communication unit 509 allows the electronic device 500 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks, and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chipset, such as a Bluetooth™ device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0201] The computing unit 501 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 501 performs the various methods and processes described above. For example, in some embodiments, the aforementioned emergency plan management method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 508. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 500 via the ROM 502 and / or the communication unit 509. In some embodiments, the computing unit 501 may be configured to perform the aforementioned emergency plan management method by any other appropriate means (e.g., by means of firmware).

[0202] The program code for implementing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code can be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0203] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0204] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0205] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0206] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0207] A computer system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other.

Claims

1. An emergency plan management method, characterized in that: The method comprises: Receive a user request, and determine a target data center corresponding to the user request; wherein the target data center is a first production data center and / or a second production data center in the business service system, and the business service system further comprises: a disaster recovery data center, wherein the second production data center is a secondary production data center of the first production data; Determine whether the target data center is abnormal according to preset evaluation conditions, and if abnormal, determine the abnormal process node, wherein the process node is each node on the flow link of the flow request in the business service system; Determine the target exception handling plan corresponding to the abnormal process node from the preset plan data set, and execute the target exception handling plan, wherein each exception handling plan is pre-written according to preset standard plan writing rules and stored in the exception handling logic file in the preset plan data set.

2. The method according to claim 1, characterized in that: The traffic link of the traffic request in the business service system includes: a first traffic link in the first production data center, and a second traffic link in the second production data center, wherein the first traffic link and the second traffic link each include at least the following process nodes: a user entry node, a unified access layer node, each system traffic entry node, each system service module node, and a database system node.

3. The method according to claim 2, characterized in that The preset evaluation condition includes: whether the IP address of the target data center is normal; the receiving of the user request and determining the target data center corresponding to the user request include: Performing domain name resolution on each of the user requests to obtain a number of IP addresses carried in each of the user requests, where each IP address corresponds to a different target data center; The determining, according to the preset evaluation condition, whether the target data center is abnormal includes: Determine whether the IP address of each target data center is normal; If only one production data center has an IP address exception, the abnormal process node is determined to be the user entry node, and a first target exception handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the first target exception handling plan includes: Shield the IP address of the abnormal production data center, forward each user request with an abnormal destination IP address to another normal production data center, and have the normal production data center respond to the user request; Alternatively, if both the IP address of the first production data center and the IP address of the second production data center are abnormal, a second target abnormality handling plan corresponding to the user entry node is determined from the preset plan data set and executed, wherein the second target abnormality handling plan includes: The IP address of the abnormal production data center is shielded, and each user request with an abnormal destination IP address is forwarded to the disaster recovery data center, and the disaster recovery data center responds to each user request.

4. The method according to claim 2, characterized in that: The service instances of each service in the business service system are respectively deployed in their corresponding instance groups according to the calling relationship between the upstream and downstream service instances. The preset evaluation conditions include: whether the calling relationship between the upstream and downstream service instances in each instance group has changed. The determining whether the target data center is abnormal according to the preset evaluation conditions includes: If there is a change in the calling relationship between the upstream and downstream service instances, determine that the abnormal process node is a unified access layer node; and determining a target instance group in which the calling relationship between the upstream and downstream service instances is changed, and a target service to which the target instance group belongs; If the target instance group is only a partial instance group of the target service, a third target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the third target exception handling plan includes: Dispatching the user request of the target instance group to other instance groups of the target service except the target instance group, and having the other instance groups respond to the user request; Alternatively, if the target instance group is all instance groups of the target service, a fourth target exception handling plan corresponding to the unified access layer node is determined from the preset plan data set and executed, and the fourth target exception handling plan includes: A standby instance group of the target service is obtained from the disaster recovery data center, and the standby instance group responds to the user request.

5. The method according to claim 2, characterized in that: There is a calling relationship between each system traffic entrance and the business service module in the business service system, and the preset evaluation condition includes: whether the naming rule of the target service received by each system traffic entrance conforms to the preset naming rule, and determining whether the target data center is abnormal according to the preset evaluation condition includes: If the naming rule of the target service received by each of the system traffic entrances does not conform to the preset naming rule, determining that the abnormal process node is the system traffic entrance node; Determine and execute the fifth target abnormality handling plan corresponding to each system traffic inlet node from the preset plan data set, wherein the fifth target abnormality handling plan includes: The name of the target service is modified to a name that complies with the preset naming rule, wherein the preset naming rule includes: the IP address of the target data center+the access port number.

6. The method according to claim 2, characterized in that The first production data center is used to respond to a user's write request, and the second production data center is used to respond to a user's read request. The preset evaluation condition includes: whether a single computer room failure occurs in the first production data center and / or the second production data center. The determining whether the target data center is abnormal according to the preset evaluation condition includes: If a single computer room failure occurs in the first production data center and / or the second production data center, a sixth target exception handling plan corresponding to the database system node is determined from the preset plan data set and executed, and the sixth target exception handling plan includes: If a single computer room failure occurs in the first production data center and / or the second production data center, the target database proxy is used to migrate user requests on the computer room where the single computer room failure occurred to a computer room where the single computer room failure has not occurred, wherein the target database proxy is a data proxy for stateless services.

7. The method according to claim 2, characterized in that The method further comprises: For each of the process nodes, a process entity is generated based on preset domain name resolution rules, inlet traffic scheduling rules, service discovery rules and custom plan execution logic, wherein the custom plan execution logic is the execution logic pre-written by each development team based on the standard plan writing rules; Generate the same plan label for the process entities corresponding to the same process nodes in the first production data center and the second production data center; The step of determining a target exception handling plan corresponding to the abnormal process node from the preset plan data set includes: According to the target plan label corresponding to the abnormal process node, the target process entity corresponding to the target plan label is determined from the preset plan data set.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: If the abnormal production data center returns to normal, stop executing the target abnormality handling plan.

9. An emergency plan management device, characterized in that: The device comprises: A user request receiving module is used to receive a user request and determine a target data center corresponding to the user request; wherein the target data center is a first production data center and / or a second production data center in the business service system, and the business service system further includes: a disaster recovery data center, wherein the second production data center is a secondary production data center of the first production data; A determination module, used to determine whether the target data center is abnormal according to a preset evaluation condition, and if abnormal, determine the abnormal process node, wherein the process node is each node on the flow link of the flow request in the business service system; The plan execution module is used to determine the target exception handling plan corresponding to the abnormal process node from the preset plan data set and execute the target exception handling plan, wherein each exception handling plan is pre-written according to the preset standard plan writing rules and stored in the exception handling logic file in the preset plan data set.

10. An electronic device, characterized in that: The electronic device comprises: Processor; and Memory for storing programs, The program includes instructions, which, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 8.

11. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to make a computer execute the method according to any one of claims 1-8.

Images