Fault handling method, processing device, electronic device and readable storage medium

Abstract

The present disclosure provides a fault handling method, which can be applied to the field of computer technology, and specifically relates to the field of system fault handling. The fault handling method includes: in the case of a fault in a first system, determining user data associated with the fault in the first system; marking the user data as whitelist user data, wherein the first system can respond to requests from other users except the whitelist user data; transferring the whitelist user data to a second system so as to perform fault isolation on the whitelist user data in the first system; and receiving the whitelist user data from the second system when the fault in the first system is repaired. The present disclosure also provides a processing device, an electronic device, and a readable storage medium.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, specifically to the field of system fault processing, and more specifically to a fault processing method, a processing device, an electronic device, a readable storage medium, and a program product. Background Art

[0002] With the continuous iteration, update and operation and maintenance of the system, various faults will inevitably be encountered during the operation of the system. The fault handling method directly affects the experience of system users and reflects the availability and reliability of the system.

[0003] In the related art, when a system fails, the entire system needs to be stopped and the failure of the system needs to be handled, which reduces the efficiency of the failure handling and poors the system user experience. Summary of the invention

[0004] In view of the above problems, the present disclosure provides a fault handling method, a processing device, an electronic device, a readable storage medium and a program product.

[0005] According to a first aspect of the present disclosure, a fault handling method is provided, comprising: in the event that a first system fails, determining user data associated with the fault in the first system; marking the user data as whitelist user data, wherein the first system is able to respond to requests from other users except the whitelist user data; transferring the whitelist user data to a second system so as to perform fault isolation on the whitelist user data in the first system; and receiving the whitelist user data from the second system when the fault in the first system is repaired.

[0006] According to an embodiment of the present disclosure, the second system includes a temporary business table and a target business table, all initial user data in the first system is transferred from the second system, and the target business table stores all initial user data in the first system; transferring the whitelist user data to the second system so as to perform fault isolation on the whitelist user data in the first system includes: transferring the whitelist user data to the temporary business table; based on the whitelist data transferred from the temporary business table, updating the initial user data in the target business table having the same primary key as the temporary business table to the whitelist data; and modifying the transaction route of the whitelist data to the second system so as to perform fault isolation on the whitelist user data in the first system.

[0007] According to an embodiment of the present disclosure, when the fault of the first system is repaired, receiving whitelist user data from the second system includes: clearing user data associated with the fault in the first system; and receiving whitelist user data from the second system based on preset logical rules.

[0008] According to an embodiment of the present disclosure, after receiving the whitelist user data from the second system, the method further includes: modifying the transaction route of the whitelist user data to the repaired first system.

[0009] According to an embodiment of the present disclosure, determining the user data associated with the fault in the first system includes: analyzing a transaction log in the first system to obtain the user data associated with the fault.

[0010] According to an embodiment of the present disclosure, marking the user data as whitelist user data includes: modifying the state of the user data associated with the fault in the first system; and marking the modified user data as whitelist user data.

[0011] According to an embodiment of the present disclosure, after marking the user data as whitelist user data, the method further includes: controlling business transactions of the whitelist user data.

[0012] A second aspect of the present disclosure provides a fault handling device, including: a determination module, used to determine user data associated with the fault in the first system when a fault occurs in the first system; a marking module, used to mark the user data as whitelist user data, wherein the first system is able to respond to requests from other users except the whitelist user data; a transfer module, used to transfer the whitelist user data to the second system so as to perform fault isolation on the whitelist user data in the first system; and a receiving module, used to receive the whitelist user data from the second system when the fault of the first system is repaired.

[0013] A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned fault handling method.

[0014] The fourth aspect of the present disclosure further provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned fault handling method.

[0015] The fifth aspect of the present disclosure further provides a computer program product, including a computer program, which implements the above-mentioned fault handling method when executed by a processor.

[0016] Through the embodiments of the present disclosure, in the case of a failure in the first system, the user data associated with the failure in the first system is determined; the user data is marked as whitelist user data, wherein the first system can respond to requests from other users except the whitelist user data; the whitelist user data is transferred to the second system so as to isolate the failure of the whitelist user data in the first system; and in the case of the first system failure being repaired, the whitelist user data from the second system is received. The technical problem in the related art that once a system fails, the normal operation of the entire system will be affected, and the user experience of the system will be reduced is solved. When a system fails, the whitelist data associated with the failure can be isolated and recovered based on the whitelist processing method, ensuring that the failure will not affect the operation of the entire system, improving the efficiency of fault handling, reducing the scope of influence of the system failure, and improving the user experience of the system. At the same time, the processing method is implemented based on the Python scripting language, which is easy to deploy and operate when a system failure occurs, and improves the efficiency of data migration. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0018] Figure 1 A schematic diagram of an application scenario of a fault handling method and a fault handling device according to an embodiment of the present disclosure is shown;

[0019] Figure 2 A flowchart of a fault handling method according to an embodiment of the present disclosure is schematically shown;

[0020] Figure 3 A flowchart schematically shows a method for transferring whitelist user data to a second system according to an embodiment of the present disclosure;

[0021] Figure 4 A schematic diagram schematically shows a fault handling method according to an embodiment of the present disclosure;

[0022] Figure 5 A structural block diagram of a fault handling device according to an embodiment of the present disclosure is schematically shown; and

[0023] Figure 6 A block diagram of an electronic device suitable for implementing a fault handling method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0024] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0025] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0026] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0027] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0028] During the system upgrade process, for some important systems, the parallel verification phase of the new and old systems is essential. In this state, both the new and old systems provide external services. The old system has been verified in long-term actual business scenarios and is in a stable operating state. During the launch of the new system, it has not been verified in long-term actual business scenarios, and the probability of failure is high. When a failure occurs, it is necessary to handle the failure efficiently and stably to reduce the impact of the failure and improve the user experience of the system users.

[0029] To this end, the embodiments of the present disclosure provide a fault handling method, a processing device, an electronic device, a readable storage medium, and a program product. The fault handling method includes: in the case of a fault in a first system, determining user data associated with the fault in the first system; marking the user data as whitelist user data, wherein the first system can respond to requests of other users except the whitelist user data; transferring the whitelist user data to a second system so as to perform fault isolation on the whitelist user data in the first system; and receiving the whitelist user data from the second system when the fault in the first system is repaired.

[0030] In the technical solution of the present disclosure, the collection, storage, use, processing, transmission, provision, disclosure and application of user personal information involved comply with the provisions of relevant laws and regulations, take necessary confidentiality measures, and do not violate public order and good morals.

[0031] In the technical solution of the present disclosure, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.

[0032] Figure 1 The application scenario diagram of the fault handling method and the processing device according to the embodiment of the present disclosure is schematically shown.

[0033] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a first system 101 and a second system 102. The first system 101 includes multiple servers, namely, servers 1011, 1012, 1013, etc., and the second system 102 includes multiple servers, namely, servers 1021, 1022, 1023, etc.

[0034] The servers in the first system 101 and the second system 102 are servers that provide various services. For example, they are backend management servers that provide support for services handled by users (for example only). The backend management server can analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, service handling results or data, etc. obtained or generated according to user requests) to the user.

[0035] The first system 101 and the second system 102 are in a state of parallel operation, and the first initialization user data in the first system 101 is transferred from the first part of the user data in all the user data in the second system. After the first system runs stably, the second part of the user data in the second system other than the first part of the user data is transferred to the first system as the second initial user data, and after the first system 101 runs stably, all the user data in the second system 102 are transferred to the first system in sequence, so that the first system is verified by the actual business scenario and reaches a stable operation state.

[0036] During the parallel operation of the first system 101 and the second system 102, if a fault occurs in the first system 101, the user data associated with the fault in the first system 101 can be transferred to the second system 102 as whitelist user data. After the fault in the first system 101 is repaired, the whitelist data in 102 can be transferred to the first system.

[0037] It should be noted that a fault handling method provided in the embodiment of the present disclosure can generally be executed by a server in the first system 101 and the second system 102, or by a server cluster in the first system 101 and the second system 102. Accordingly, a fault handling device provided in the embodiment of the present disclosure can generally be set in a server in the first system 101 and the second system 102, or in a server cluster in the first system 101 and the second system 102.

[0038] It should be understood that Figure 1 The number of systems and servers in the embodiment is only for illustration. Any number of systems and servers may be provided according to implementation requirements.

[0039] The following will be based on Figure 1 The scene described by Figure 2 to Figure 4 The fault handling method of the disclosed embodiment is described in detail.

[0040] In the technical solution disclosed in the present invention, the acquisition, collection, storage, use, processing, transmission, provision, disclosure and application of data are in compliance with the provisions of relevant laws and regulations, necessary confidentiality measures are taken, and do not violate public order and good morals.

[0041] Figure 2 The flowchart of the fault handling method according to the embodiment of the present disclosure is schematically shown.

[0042] like Figure 2 As shown, the fault handling method of this embodiment includes operations S210 to S240.

[0043] In operation S210 , in the case where a failure occurs in the first system, user data associated with the failure in the first system is determined.

[0044] According to an embodiment of the present disclosure, the failure of the first system may include: a hardware failure, a software program failure, a network failure, a subsystem operation failure, etc. of the system.

[0045] According to an embodiment of the present disclosure, user data may include user identification information and service information corresponding to the user identification information.

[0046] It should be noted that in the technical solution of the present disclosure, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.

[0047] According to an embodiment of the present disclosure, during the operation of the first system, when a fault occurs in the first system, in order to troubleshoot and repair the fault in the first system, it is first necessary to determine the user data associated with the fault, so that the fault can be subsequently located and repaired after the user data associated with the fault is isolated.

[0048] In operation S220, the user data is marked as whitelist user data, wherein the first system is able to respond to requests of other users except the whitelist user data.

[0049] According to an embodiment of the present disclosure, the whitelist user data refers to user data associated with a fault that needs to be processed, while other associated user data without a fault does not belong to the whitelist user data.

[0050] According to an embodiment of the present disclosure, for a user request that does not belong to the whitelist user data, the first system can operate normally for the user request that does not belong to the whitelist user data and respond to the user request.

[0051] According to the embodiment of the present disclosure, after marking the user data as whitelist user data, the business transactions of the whitelist user data are controlled. That is, all transactions of the whitelist user data are rejected, and at the same time, a status reminder of prohibited transaction operations is displayed to the outside through the external interface.

[0052] In operation S230, the whitelist user data is transferred to the second system so as to perform fault isolation on the whitelist user data in the first system.

[0053] According to an embodiment of the present disclosure, fault isolation can be used to isolate and individually repair problematic parts when problems occur in some applications or subsystems in the first system, so that other applications or subsystems in the first system can operate normally and will not be affected by the isolated faults.

[0054] According to an embodiment of the present disclosure, the whitelist user data is part of the user data in the first system, and is user data associated with the fault.

[0055] According to an embodiment of the present disclosure, transferring the whitelist user data to the second system may include: migrating the whitelist user data and changing the transaction route of the whitelist user data.

[0056] In operation S240 , when the first system fails and is repaired, whitelist user data is received from the second system.

[0057] According to an embodiment of the present disclosure, after the whitelist user data is transferred to the second system, the whitelist user data will be run on the second system. At the same time, the fault of the first system is located and repaired. After the repair is completed, the whitelist user data transferred to the second system is transferred to the first system again to facilitate the fault recovery of the whitelist user data on the first system.

[0058] According to the embodiments of the present disclosure, fault recovery can be the strategy, method and technology adopted to isolate the fault after the fault is detected in the first system, and select a preset method to return the first system to the task point before the fault is repaired, so that the first system continues to work.

[0059] Through the embodiments of the present disclosure, in the case of a failure in the first system, the user data associated with the failure in the first system is determined; the user data is marked as whitelist user data, wherein the first system can respond to requests from other users except the whitelist user data; the whitelist user data is transferred to the second system so as to isolate the failure of the whitelist user data in the first system; and in the case of the first system failure being repaired, the whitelist user data from the second system is received. The technical problem in the related art that once a system fails, the normal operation of the entire system will be affected, and the user experience of the system will be reduced is solved. When a system fails, the whitelist data associated with the failure can be isolated and recovered based on the whitelist processing method, ensuring that the failure will not affect the operation of the entire system, improving the efficiency of fault handling, reducing the scope of influence of the system failure, and improving the user experience of the system. At the same time, the processing method is implemented based on the Python scripting language, which is easy to deploy and operate when a system failure occurs, and improves the efficiency of data migration.

[0060] According to an embodiment of the present disclosure, the second system includes a temporary service table and a target service table, the initial user data in the first system is transferred from the second system, and the target service table stores the initial user data in the first system.

[0061] According to an embodiment of the present disclosure, the second system and the first system are parallel systems, the first system and the second system are in a parallel operation state, the initialization user data in the first system is part of the user data of all the user data in the second system transferred thereto, and the second system retains the initialization user data in the first system. The initialization user data in the first system is all the user data in the first system.

[0062] According to an embodiment of the present disclosure, the temporary service table can be used to store the whitelist user data when the whitelist user data in the first system is transferred to the second system.

[0063] Figure 3 The flowchart of the method for transferring whitelist user data to the second system according to an embodiment of the present disclosure is schematically shown.

[0064] like Figure 3 As shown, the method may include operations S310 to S330.

[0065] In operation S310, whitelist user data is transferred to a temporary service table.

[0066] According to an embodiment of the present disclosure, transferring the whitelist data to the temporary service table may be achieved by using Structured Query Language (Structured Query Language).

[0067] According to an embodiment of the present disclosure, the structured query language may be a database query and programming language, which may be used to access data and query, update, and manage a relational database system.

[0068] In operation S320 , based on the whitelist data transferred from the temporary service table, the initial user data in the target service table having the same primary key as that in the temporary service table is updated to the whitelist data.

[0069] According to an embodiment of the present disclosure, a primary key is a unique keyword, which can be one or more fields in a data table, and the value of the primary key is used to uniquely identify a record in the table. For example, in a relationship between two tables, a primary key is used to reference a specific record in one table from another table.

[0070] According to an embodiment of the present disclosure, for example, user data with the same primary key information in the temporary business table and the target business table are merged to reference the whitelist user data from the temporary business table in the target business table, so as to update the initial user data in the target business to the whitelist user data.

[0071] According to the embodiments of the present disclosure, for data that does not correspond to the primary key information in the temporary business table, the whitelist data in the temporary business table can be directly inserted into the target business table to implement the data update operation in the target business table.

[0072] According to an embodiment of the present disclosure, when whitelist user data is transferred to the second system, since the whitelist user data in the first system has been running in the first system for a period of time, some meaningless data or dirty data will be generated. For these meaningless data or dirty data, these meaningless data or dirty data can be deleted during the transfer to the second system.

[0073] In operation S330, the transaction route of the whitelist data is modified to the second system, so as to perform fault isolation on the whitelist user data in the first system.

[0074] According to an embodiment of the present disclosure, transaction routing refers to controlling a transaction path of user data, that is, whether the user data runs in a first system or a second system.

[0075] According to an embodiment of the present disclosure, information configuration is performed using a preset programming language and a file in a preset format to achieve migration of whitelist user data and modify the transaction route of the whitelist data from the first system to the second system, so as to facilitate fault isolation of the whitelist data of the first system.

[0076] According to an embodiment of the present disclosure, after the transaction route of the whitelist user data is modified, a contact operation is performed on the transaction of the whitelist user data, so that the whitelist user data runs normally in the second system.

[0077] According to an embodiment of the present disclosure, when a fault in the first system is repaired, receiving whitelist user data from the second system includes: clearing user data associated with the fault in the first system; and receiving whitelist user data from the second system based on preset logical rules.

[0078] According to an embodiment of the present disclosure, after the whitelist data is transferred to the second system, repairing the first system fault may include accurately locating the first system fault and repairing and resolving the located fault.

[0079] According to an embodiment of the present disclosure, after the fault of the first system is repaired, user data associated with the fault in the first system is cleared, that is, the whitelist data before being transferred to the second system.

[0080] It should be noted that clearing the user data associated with the fault in the first system may be clearing the user data associated with the fault in the first system while transferring the whitelist user data to the second system, or may be clearing the user data associated with the fault in the first system before receiving the whitelist user data from the second system. In the embodiments of the present disclosure, no specific limitation is made.

[0081] According to an embodiment of the present disclosure, the user data in the target business table of the second system is filtered to obtain whitelist user data. The business transactions corresponding to the whitelist user data in the second system are controlled, and the transactions of the whitelist user data are rejected. Similarly, a status reminder of prohibited transaction operations is displayed to the outside through an external interface.

[0082] According to an embodiment of the present disclosure, the whitelist user data in the second system is transferred to the first system in which the fault has been repaired through structured query language.

[0083] According to an embodiment of the present disclosure, after receiving the whitelist user data from the second system, the method further includes: modifying the transaction route of the whitelist user data to the repaired first system.

[0084] According to an embodiment of the present disclosure, after the transaction route of the whitelist user data transferred to the first system is modified from the second system to the first system, the transaction operation rejecting the whitelist user data is released, so that the whitelist user data can operate normally in the repaired first system.

[0085] According to an embodiment of the present disclosure, determining the user data associated with the fault in the first system includes: analyzing a transaction log in the first system to obtain the user data associated with the fault.

[0086] According to an embodiment of the present disclosure, when determining user data associated with a fault in the first system, firstly, log transaction information of all user data in the first system can be obtained, and then the log transaction information can be analyzed and processed to filter out error information associated with the fault, and then the user data associated with the fault can be determined based on the error information.

[0087] According to an embodiment of the present disclosure, marking user data as whitelist user data includes: modifying a state of user data associated with a fault in the first system; and marking the modified user data as whitelist user data.

[0088] According to an embodiment of the present disclosure, the status of user data may include being able to run and being controlled to run. For example, the state of being able to run is represented by “Y”; the state of being refused to run is represented by “N”.

[0089] According to an embodiment of the present disclosure, when the first system does not fail, all user data in the first system are in an operational state. When the first system fails, after determining the user data associated with the failure, the state of the user data associated with the failure is changed from operational "Y" to refusal to run "N", and the user data is marked as whitelist user data.

[0090] According to an embodiment of the present disclosure, the fault handling method can be implemented based on Python scripting language.

[0091] According to the embodiments of the present disclosure, the fault handling method is implemented by writing in Python scripting language, so that the configuration deployment is convenient and flexible when a fault occurs, and the efficiency is improved when performing data migration. It can be applied to a variety of flexible migration scenarios, making the fault handling method more widely applicable.

[0092] Figure 4 A schematic diagram of a fault handling method according to an embodiment of the present disclosure is schematically shown.

[0093] like Figure 4 As shown, under the premise that a fault occurs in the first system 401, the user data 4011 associated with the fault in the first system 401 is determined, the user data 4011 is marked as whitelist user data 402, and the whitelist user data 402 is transferred to the second system 403 so as to perform fault isolation on the whitelist user data 402. When the fault of the first system is repaired, the whitelist user data in the second system 403 is transferred to the first system 401.

[0094] Based on the above fault handling method, the present disclosure also provides a fault handling device. Figure 5 The device is described in detail.

[0095] Figure 5 The structural block diagram of the fault handling device according to the embodiment of the present disclosure is schematically shown.

[0096] like Figure 5 As shown, the fault handling device 500 of this embodiment may include a determination module 510 , a marking module 520 , a transfer module 530 and a receiving module 540 .

[0097] The determination module 510 is used to determine the user data associated with the fault in the first system when the first system fails. In one embodiment, the determination module 510 can be used to perform the operation S210 described above, which will not be described in detail here.

[0098] The marking module 520 is used to mark the user data as whitelist user data, wherein the first system can respond to requests of other users except the whitelist user data. In one embodiment, the marking module 520 can be used to perform the operation S220 described above, which will not be repeated here.

[0099] The transfer module 530 is used to transfer the whitelist user data to the second system so as to perform fault isolation on the whitelist user data in the first system. In one embodiment, the transfer module 530 can be used to perform the operation S230 described above, which will not be described in detail here.

[0100] The receiving module 540 is used to receive the whitelist user data from the second system when the first system fails and is repaired. In one embodiment, the receiving module 540 can be used to perform the operation S240 described above, which will not be described in detail here.

[0101] Through the embodiments of the present disclosure, in the case of a failure in the first system, the user data associated with the failure in the first system is determined; the user data is marked as whitelist user data, wherein the first system can respond to requests from other users except the whitelist user data; the whitelist user data is transferred to the second system so as to isolate the failure of the whitelist user data in the first system; and in the case of the first system failure being repaired, the whitelist user data from the second system is received. The technical problem in the related art that once a system fails, the normal operation of the entire system will be affected, and the user experience of the system will be reduced is solved. When a system fails, the whitelist data associated with the failure can be isolated and recovered based on the whitelist processing method, ensuring that the failure will not affect the operation of the entire system, improving the efficiency of fault handling, reducing the scope of influence of the system failure, and improving the user experience of the system. At the same time, the processing method is implemented based on the Python scripting language, which is easy to deploy and operate when a system failure occurs, and improves the efficiency of data migration.

[0102] According to an embodiment of the present disclosure, the second system includes a temporary service table and a target service table, all initial user data in the first system is transferred from the second system, and the target service table stores all initial user data in the first system.

[0103] According to an embodiment of the present disclosure, the transfer module 530 may include: a transfer submodule, an update submodule, and a first modification submodule.

[0104] The transfer submodule is used to transfer the whitelist user data to the temporary business table.

[0105] The update submodule is used to update the initial user data in the target business table with the same primary key as the temporary business table to the whitelist data based on the whitelist data transferred in the temporary business table.

[0106] The first modification submodule is used to modify the transaction route of the whitelist data to the second system, so as to perform fault isolation on the whitelist user data in the first system.

[0107] According to an embodiment of the present disclosure, the receiving module 530 may include: a clearing submodule and a receiving submodule.

[0108] The clearing submodule is used to clear the user data associated with the fault in the first system.

[0109] The receiving submodule is used to receive whitelist user data from the second system based on preset logical rules.

[0110] According to an embodiment of the present disclosure, after receiving the whitelist user data from the second system, the method further includes: modifying the transaction route of the whitelist user data to the repaired first system.

[0111] According to an embodiment of the present disclosure, the determination module 510 may include: an analysis submodule.

[0112] The analysis submodule is used to analyze the transaction log in the first system to obtain user data associated with the fault.

[0113] According to an embodiment of the present disclosure, the marking module 520 may include: a second modifying submodule and a marking submodule.

[0114] The second modification submodule is used to modify the state of the user data associated with the fault in the first system.

[0115] The marking submodule is used to mark the modified user data as whitelist user data.

[0116] According to an embodiment of the present disclosure, after marking the user data as whitelist user data, the method further includes: controlling business transactions of the whitelist user data.

[0117] According to an embodiment of the present disclosure, any multiple modules of the determination module 510, the marking module 520, the transfer module 530 and the receiving module 540 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the determination module 510, the marking module 520, the transfer module 530 and the receiving module 540 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, at least one of the determination module 510, the marking module 520, the transfer module 530 and the receiving module 540 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be performed.

[0118] Figure 6 A block diagram of an electronic device suitable for implementing a fault handling method according to an embodiment of the present disclosure is schematically shown.

[0119] like Figure 6 As shown, the electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include an onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0120] In RAM 603, various programs and data required for the operation of electronic device 600 are stored. Processor 601, ROM 602 and RAM 603 are connected to each other via bus 604. Processor 601 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 602 and / or RAM 603. It should be noted that the program can also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.

[0121] According to an embodiment of the present disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to the bus 604. The electronic device 600 may further include one or more of the following components connected to the I / O interface 605: an input portion 606 including a keyboard, a mouse, etc.; an output portion 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 608 including a hard disk, etc.; and a communication portion 609 including a network interface card such as a LAN card, a modem, etc. The communication portion 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage portion 608 as needed.

[0122] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0123] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: 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), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 602 and / or RAM 603 described above and / or one or more memories other than ROM 602 and RAM 603.

[0124] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the fault handling method provided by the embodiment of the present disclosure.

[0125] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 601. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0126] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 609, and / or installed from a removable medium 611. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0127] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, apparatus, module, unit, etc. described above can be implemented by a computer program module.

[0128] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0129] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0130] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0131] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A fault handling method, include: In the event of a failure in the first system, determining user data in the first system associated with the failure; marking the user data as whitelist user data, wherein the first system is able to respond to requests from other users except the whitelist user data; transferring the whitelist user data to a second system so as to perform fault isolation on the whitelist user data in the first system, wherein the second system and the first system are in parallel operation, the second system comprises a temporary service table and a target service table, and the target service table stores all the initial user data in the first system; and When the first system fails and is repaired, receiving the whitelist user data from the second system; The transferring of the whitelist user data to the second system so as to perform fault isolation on the whitelist user data in the first system includes: Transferring the whitelist user data to the temporary service table; Based on the whitelist data transferred from the temporary service table, updating the initial user data in the target service table having the same primary key as that in the temporary service table to the whitelist data; The transaction route of the whitelist data is modified to the second system, so that the whitelist user data can run normally in the second system, and so that fault isolation can be performed on the whitelist user data in the first system.

2. The method according to claim 1, in, All original user data in the first system is transferred from the second system.

3. The method according to claim 1, in, In the case where the first system fails and is repaired, receiving the whitelist user data from the second system includes: clearing user data associated with the fault in the first system; Based on preset logical rules, the whitelist user data is received from the second system.

4. The method according to claim 1, after receiving the whitelist user data from the second system, further comprising: include: Modify the transaction route of the whitelist user data to the repaired first system.

5. The method according to claim 1, in, Determining user data associated with the fault in the first system includes: Analyze the transaction log in the first system to obtain user data associated with the fault.

6. The method according to claim 1, in, The step of marking the user data as whitelist user data comprises: modifying a state of user data associated with the fault in the first system; The modified user data is marked as whitelist user data.

7. The method according to claim 1, after marking the user data as whitelist user data, further comprising: include: Control business transactions of the whitelisted user data.

8. According to the method according to any one of claims 1 to 7, the fault handling method is implemented based on Python scripting language.

9. A fault handling device, include: A determination module, configured to determine user data associated with a fault in the first system when a fault occurs in the first system; a marking module, configured to mark the user data as whitelist user data, wherein the first system is capable of responding to requests of other users except the whitelist user data; a transfer module, configured to transfer the whitelist user data to a second system, so as to perform fault isolation on the whitelist user data in the first system, wherein the second system and the first system are in a parallel operation state, the second system comprises a temporary service table and a target service table, and the target service table stores all the initial user data in the first system; and A receiving module, configured to receive the whitelist user data from the second system when the first system fails and is repaired; The transfer module includes: A transfer submodule, used for transferring the whitelist user data to the temporary service table; An updating submodule, configured to update the initial user data in the target service table having the same primary key as that in the temporary service table to the whitelist data based on the whitelist data transferred from the temporary service table; The first modification submodule is used to modify the transaction route of the whitelist data to the second system, so that the whitelist user data can run normally in the second system, and to perform fault isolation on the whitelist user data in the first system.

10. An electronic device, include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors execute the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 8.

12. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images