CN114138564A - Fault handling method, processing device, electronic device and readable storage medium - Google Patents
Fault handling method, processing device, electronic device and readable storage medium Download PDFInfo
- Publication number
- CN114138564A CN114138564A CN202111487776.7A CN202111487776A CN114138564A CN 114138564 A CN114138564 A CN 114138564A CN 202111487776 A CN202111487776 A CN 202111487776A CN 114138564 A CN114138564 A CN 114138564A
- Authority
- CN
- China
- Prior art keywords
- user data
- white list
- fault
- list user
- present disclosure
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operations
- G06F11/1479—Generic software techniques for error detection or fault masking
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operations
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/142—Reconfiguring to eliminate the error
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
Abstract
The disclosure provides a fault processing method, which can be applied to the technical field of computers, and particularly relates to the field of system fault processing. The fault processing method comprises the following steps: in the event of a failure of the first system, determining user data associated with the failure in the first system; marking the user data as white list user data, wherein the first system is capable of responding to requests of other users except the white list user data; transferring the white list user data to a second system so as to isolate the white list user data in the first system from faults; in the event of a first system failure fix, white list user data is received from a second system. The disclosure also provides a processing device, an electronic device and a readable storage medium.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to the field of system fault handling, and more particularly, to a fault handling method, a processing apparatus, an electronic device, a readable storage medium, and a program product.
Background
With the continuous iterative update and operation and maintenance of the system, various faults are inevitably encountered in the operation process of the system, and the fault processing method directly influences the experience of system users and reflects the availability and reliability of the system.
In the related art, when a system fails, the whole system needs to be stopped to process the failure of the system, so that the failure processing efficiency is reduced, and the user experience of the system is poor.
Disclosure of Invention
In view of the above, the present disclosure provides a fault handling method, a processing apparatus, an electronic device, a readable storage medium, and a program product.
According to a first aspect of the present disclosure, there is provided a fault handling method, including: in the event of a failure of the first system, determining user data associated with the failure in the first system; marking the user data as white list user data, wherein the first system is capable of responding to requests of other users except the white list user data; transferring the white list user data to a second system so as to isolate the white list user data in the first system from faults; in the event of a first system failure fix, white list user data is received from a second system.
According to the embodiment of the present disclosure, the second system includes a temporary service table and a target service table, all the initial user data in the first system is transferred from the second system, and all the initial user data in the first system is stored in the target service table; transferring the white list user data to a second system so as to isolate the white list user data in the first system from faults, comprising: transferring the white list user data to the temporary service list; updating initial user data in a target service table which is the same as a main key in the temporary service table into white list data based on the white list data transferred in the temporary service table; and modifying the transaction route of the white list data to the second system so as to carry out fault isolation on the white list user data in the first system.
According to an embodiment of the present disclosure, wherein receiving white list user data from a second system in case of a first system failover, comprises: clearing user data associated with the fault in the first system; white list user data is received from the second system based on a preset logic rule.
According to the embodiment of the present disclosure, after receiving the white list user data from the second system, the method further includes: transaction routing of the white list user data is modified to the repaired first system.
According to an embodiment of the present disclosure, wherein determining user data associated with the fault in the first system comprises: the transaction log in the first system is analyzed to obtain user data associated with the fault.
According to an embodiment of the present disclosure, wherein marking user data as white list user data comprises: modifying a state of user data associated with the fault in the first system; and marking the modified user data as white list user data.
According to the embodiment of the present disclosure, after marking the user data as white list user data, the method further includes: and controlling business transaction of the white list user data.
A second aspect of the present disclosure provides a fault handling apparatus comprising: the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining user data associated with a fault in a first system under the condition that the first system has the fault; the system comprises a marking module, a data processing module and a data processing module, wherein the marking module is used for marking user data as white list user data, and the first system can respond to requests of other users except the white list user data; the transfer module is used for transferring the white list user data to a second system so as to carry out fault isolation on the white list user data in the first system; and a receiving module, configured to receive the white list user data from the second system when the first system is in fault recovery.
A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the fault handling method described above.
The fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-mentioned fault handling method.
A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the above-described fault handling method.
According to the embodiment of the disclosure, in the case that the first system fails, determining user data associated with the failure in the first system; marking the user data as white list user data, wherein the first system is capable of responding to requests of other users except the white list user data; transferring the white list user data to a second system so as to isolate the white list user data in the first system from faults; in the event of a first system failure fix, white list user data is received from a second system. The method and the device solve the technical problems that in the related art, once the system fails, the normal operation of the whole system is influenced, and the user experience of the system is reduced. The processing method has the advantages that when the system fails, the white list data associated with the failure are subjected to fault isolation and fault recovery based on the white list processing mode, the fact that the operation of the whole system is not affected by the occurring failure is guaranteed, the fault processing efficiency is improved, the influence range of the system failure is reduced, the system user experience is improved, meanwhile, the processing method is written and realized based on the Python scripting language, when the system failure occurs, the deployment is convenient, the operation is convenient and fast, and the data migration efficiency is improved.
Drawings
The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:
fig. 1 schematically illustrates an application scenario diagram of a fault handling method and a handling apparatus according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a fault handling method according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a flow chart of a method of transferring whitelist user data to a second system, in accordance with an embodiment of the disclosure;
FIG. 4 schematically illustrates a schematic diagram of a fault handling method according to an embodiment of the disclosure;
fig. 5 schematically shows a block diagram of a fault handling apparatus according to an embodiment of the present disclosure; and
fig. 6 schematically shows a block diagram of an electronic device adapted to implement a fault handling method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
In the upgrading and updating process of the system, for some important systems, the parallel verification stage of the new system and the old system is indispensable, in the state, the new system and the old system both provide services to the outside, and the old system is verified by a long-term actual service scene, so that the running state is stable. In the on-line process of the new system, long-term verification of a long-term actual service scene is not carried out, and the probability of faults is high. When a fault occurs, the fault needs to be efficiently and stably processed, the influence range of the fault is reduced, and the use experience of a system user is improved.
To this end, the disclosed embodiments provide a fault handling method, a handling apparatus, an electronic device, a readable storage medium, and a program product. The fault processing method comprises the following steps: in the event of a failure of the first system, determining user data associated with the failure in the first system; marking the user data as white list user data, wherein the first system is capable of responding to requests of other users except the white list user data; transferring the white list user data to a second system so as to isolate the white list user data in the first system from faults; in the event of a first system failure fix, white list user data is received from a second system.
In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure, application and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations, necessary confidentiality measures are taken, and the customs of the public order is not violated.
In the technical scheme of the disclosure, before the personal information of the user is acquired or collected, the authorization or the consent of the user is acquired.
Fig. 1 schematically shows an application scenario diagram of a fault handling method and a handling apparatus according to an embodiment of the present disclosure.
As shown in fig. 1, an application scenario 100 according to this embodiment may include a first system 101 and a second system 102. The first system 101 includes a plurality of servers, i.e., servers 1011, 1012, 1013, etc., and the second system 102 includes a plurality of servers, i.e., servers 1021, 1022, 1023, etc.
The servers in the first system 101 and the second system 102 are each a server that provides various services. For example, a background management server (for example only) that provides support for the services handled by the user. The background management server may analyze and process the received data such as the user request, and feed back a processing result (e.g., a webpage, information, a service transaction result or data obtained or generated according to the user request) to the user.
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 all user data in the second system. After the first system operates stably, transferring a second part of user data in other user data out of the first part of user data in the second system to the first system as second initial user data, and after the first system 101 operates stably, sequentially transferring all the user data in the second system 102 to the first system, so that the first system achieves a stable operation state through verification of an actual service scene.
In the process of parallel operation of the first system 101 and the second system 102, if a fault occurs in the first system 101, user data associated with the fault in the first system 101 may be transferred to the second system 102 as white list user data, and after the fault of the first system 101 is repaired, the white list data transferred to the second system 102 is transferred to the first system.
It should be noted that, a fault handling method provided by the embodiment of the present disclosure may be generally executed by a certain server in the first system 101 and the second system 102, or may be executed by a server cluster in the first system 101 and the second system 102. Accordingly, a fault handling apparatus provided by the embodiment of the present disclosure may be generally disposed in a certain server in the first system 101 and the second system 102, or may be disposed in a server cluster in the first system 101 and the second system 102.
It should be understood that the number of systems and servers in FIG. 1 is merely illustrative. There may be any number of systems and servers, as desired for implementation.
The fault handling method of the disclosed embodiment will be described in detail below with fig. 2 to 4 based on the scenario described in fig. 1.
In the technical scheme of the disclosure, the data acquisition, collection, storage, use, processing, transmission, provision, disclosure, application and other processing are all in accordance with the regulations of relevant laws and regulations, necessary security measures are taken, and the public order and good custom are not violated.
Fig. 2 schematically shows a flow chart of a fault handling method according to an embodiment of the present disclosure.
As shown in fig. 2, the fault handling method of this embodiment includes operations S210 to S240.
In operation S210, in case of a failure of the first system, user data associated with the failure in the first system is determined.
According to an embodiment of the present disclosure, the first system failure may include: hardware faults of the system, software program faults, network faults, subsystem operation faults and the like.
According to the embodiment of the disclosure, the user data may include user identification information and service information corresponding to the user identification information.
It should be noted that, in the technical solution of the present disclosure, before acquiring or collecting the personal information of the user, the authorization or the consent of the user is obtained.
According to the embodiment of the disclosure, in the operation process of the first system, when the first system has a fault, in order to troubleshoot and repair the fault occurring in the first system, the user data associated with the fault needs to be determined first, so that the fault can be located and repaired after the user data associated with the fault is fault-isolated.
In operation S220, the user data is marked as white-listed user data, wherein the first system is capable of responding to requests of other users than the white-listed user data.
According to an embodiment of the present disclosure, white list user data refers to user data associated with a fault that needs to be handled. While other non-failing associated user data do not belong to the white list user data.
According to the embodiment of the disclosure, for the user request not belonging to the white list user data, the first system can normally operate for the user request not belonging to the white list user data, and respond to the user request.
According to an embodiment of the present disclosure, after the user data is marked as white list user data, the business transaction of the white list user data is controlled. Namely, the transactions of the white list user data are all rejected, and meanwhile, the state prompt for forbidding transaction operation is displayed to the outside through the external interface.
In operation S230, the white list user data is transferred to the second system so as to perform fault isolation on the white list user data in the first system.
According to the embodiment of the disclosure, fault isolation can be implemented by isolating and independently repairing a part of an application or a subsystem in a first system when the part of the application or the subsystem in the first system has a problem, so that other applications or subsystems in the first system can normally operate and cannot be affected by the isolated fault.
According to an embodiment of the present disclosure, the white list user data is part of the user data in the first system, the user data associated with the failure.
According to an embodiment of the present disclosure, transferring white list user data to the second system may include: migration of white list user data and alteration of transaction routing of white list user data.
In operation S240, in case of the first system failure repair, white list user data from the second system is received.
According to the embodiment of the disclosure, after the white list user data is transferred to the second system, the white list user data is operated on the second system, meanwhile, the fault of the first system is positioned and repaired, and after the repair is completed, the white list user data transferred to the second system is transferred to the first system again, so that the white list user data can be recovered on the first system.
According to the embodiment of the disclosure, the fault recovery may be implemented by isolating the fault after the fault is detected for the first system, and selecting a preset method to return the first system to a task point before the fault after the fault is repaired, so that the first system continues to work by using the strategy, method and technology.
According to the embodiment of the disclosure, in the case that the first system fails, determining user data associated with the failure in the first system; marking the user data as white list user data, wherein the first system is capable of responding to requests of other users except the white list user data; transferring the white list user data to a second system so as to isolate the white list user data in the first system from faults; in the event of a first system failure fix, white list user data is received from a second system. The method and the device solve the technical problems that in the related art, once the system fails, the normal operation of the whole system is influenced, and the user experience of the system is reduced. The processing method has the advantages that when the system fails, the white list data associated with the failure are subjected to fault isolation and fault recovery based on the white list processing mode, the fact that the operation of the whole system is not affected by the occurring failure is guaranteed, the fault processing efficiency is improved, the influence range of the system failure is reduced, the system user experience is improved, meanwhile, the processing method is written and realized based on the Python scripting language, when the system failure occurs, the deployment is convenient, the operation is convenient and fast, and the data migration efficiency is improved.
According to the embodiment of the disclosure, the second system comprises 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.
According to the embodiment of the present disclosure, the second system and the first system belong to a parallel system, the first system and the second system are in a parallel operation state, the initialization user data in the first system is transferred from part of all the user data in the second system, and the initialization user data in the first system is retained in the second system. The initialization user data in the first system is all user data in the first system.
According to the embodiment of the disclosure, the temporary service table may be used to store the white list user data when transferring the white list user data in the first system to the second system.
Fig. 3 schematically illustrates a flow chart of a method of transferring whitelist user data to a second system according to an embodiment of the disclosure.
As shown in fig. 3, the method may include operations S310 to S330.
In operation S310, the white list user data is transferred to the temporary service table.
According to an embodiment of the present disclosure, transferring white list data into the temporary business table may be achieved by using a Structured Query Language (Structured Query Language).
According to embodiments of the present disclosure, the structured query language may be a database query and programming language that may be used to access data as well as query, update, and manage a relational database system.
In operation S320, initial user data in the target service table, which is the same as the primary key in the temporary service table, is updated to white list data based on the transferred white list data in the temporary service table.
According to an embodiment of the present disclosure, the primary key is a unique key, which may 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 two-table relationship, the primary key is used to reference a particular record in one table from the other table.
According to the embodiment of the present disclosure, for example, merging operation is performed on user data with the same primary key information of the temporary service table and the target service table, so as to refer to white list user data from the temporary service table in the target service table, so as to update initial user data in the target service to the white list user data.
According to the embodiment of the disclosure, for data which does not have the primary key information in the temporary service table, the white list data in the temporary service table can be directly inserted into the target service table, so as to realize the data updating operation in the target service table.
According to the embodiment of the disclosure, when transferring the white list user data to the second system, since the white list user data in the first system runs in the first system for a period of time, part of meaningless data or dirty data may be generated, and for the meaningless data or the dirty data, a deletion operation may be performed on the meaningless data or the dirty data during the transfer to the second system.
In operation S330, a transaction route of the white list data is modified to the second system so as to perform fault isolation on the white list user data in the first system.
According to an embodiment of the present disclosure, transaction routing refers to controlling a transaction path of user data, i.e., whether the user data is operating at a first system or a second system.
According to the embodiment of the disclosure, information configuration is performed by using a preset programming language and a file form with a preset format, migration of white list user data is realized, and a transaction route of the white list data is modified from a first system to a second system, so that fault isolation is performed on the white list data of the first system.
According to the embodiment of the disclosure, after the transaction route of the white list user data is modified, the contact operation is performed on the transaction of the white list user data, so that the white list user data normally operates in the second system.
According to an embodiment of the present disclosure, receiving white list user data from a second system in case of a first system failover includes: clearing user data associated with the fault in the first system; white list user data is received from the second system based on a preset logic rule.
According to an embodiment of the present disclosure, after transferring the white list data to the second system, repairing the first system fault may include accurately locating the first system fault and repairing and solving the located fault.
According to an embodiment of the present disclosure, after the first system failure is repaired, user data associated with the failure in the first system is cleared, i.e., the previous whitelist data is transferred to the second system.
It should be noted that clearing user data associated with a failure in the first system may be done while transferring white list user data to the second system, or may be done before receiving white list user data from the second system. In the embodiments of the present disclosure, there is no particular limitation.
According to the embodiment of the disclosure, the user data in the target service table of the second system is filtered to obtain the white list user data. And controlling the business transaction corresponding to the white list user data in the second system, rejecting the transaction of the white list user data, and displaying a state prompt for forbidding transaction operation to the outside through the external interface.
According to the embodiment of the disclosure, the white list user data in the second system is transferred to the first system with the repaired fault through the structured query language.
According to an embodiment of the present disclosure, after receiving the white list user data from the second system, the method further includes: transaction routing of the white list user data is modified to the repaired first system.
According to the embodiment of the disclosure, after the transaction route of the white list user data transferred to the first system is modified from the second system to the first system, the transaction operation of rejecting the white list user data is released, so that the white list user data can normally run in the repaired first system.
According to an embodiment of the present disclosure, determining user data associated with a fault in a first system includes: the transaction log in the first system is analyzed to obtain user data associated with the fault.
According to the embodiment of the disclosure, when determining the user data associated with the fault in the first system, log transaction information of all the user data in the first system can be obtained first, then the log transaction information is analyzed, error information associated with the fault is screened out, and the user data associated with the fault is determined according to the error information.
According to an embodiment of the present disclosure, tagging user data as white list user data includes: modifying a state of user data associated with the fault in the first system; and marking the modified user data as white list user data.
According to embodiments of the present disclosure, the state of the user data may include operational and control operations, e.g., the operational state is characterized by "Y"; the status of the rejected run is characterized by "N".
According to the embodiment of the disclosure, when the first system is not in failure, the user data in the first system is in a state of being operable. 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 modified from "Y" capable of running to "N" refusal to run, and the user data is marked as white list user data.
According to the embodiment of the disclosure, the fault handling method can be written and implemented based on a Python scripting language.
According to the embodiment of the disclosure, the fault processing method is realized by writing the Python scripting language, so that the configuration and deployment are convenient and flexible when a fault occurs, the efficiency is improved when data migration is carried out, the method can be applied to various flexible migration scenes, and the fault processing method is wider in application range.
Fig. 4 schematically shows a schematic diagram of a fault handling method according to an embodiment of the present disclosure.
As shown in fig. 4, on the premise that the first system 401 has a fault, determining user data 4011 associated with the fault in the first system 401, marking the user data 4011 as white list user data 402, transferring the white list user data 402 to the second system 403 so as to isolate the white list user data 402 from the fault, and on the condition that the first system fault is repaired, transferring the white list user data in the second system 403 to the first system 401.
Based on the fault processing method, the disclosure also provides a fault processing device. The apparatus will be described in detail below with reference to fig. 5.
Fig. 5 schematically shows a block diagram of a fault handling device according to an embodiment of the present disclosure.
As shown in fig. 5, the fault handling apparatus 500 of this embodiment may include a determination module 510, a marking module 520, a transfer module 530, and a receiving module 540.
A determining module 510, configured to determine, in case of a failure of the first system, user data associated with the failure in the first system. In an embodiment, the determining module 510 may be configured to perform the operation S210 described above, which is not described herein again.
A tagging module 520 configured to tag the user data as white list user data, wherein the first system is capable of responding to requests from users other than the white list user data. In an embodiment, the marking module 520 may be configured to perform the operation S220 described above, which is not described herein again.
A transferring module 530, configured to transfer the white list user data to the second system, so as to perform fault isolation on the white list user data in the first system. In an embodiment, the transferring module 530 may be configured to perform the operation S230 described above, which is not described herein again.
A receiving module 540, configured to receive the white list user data from the second system in case of the first system failing to repair. In an embodiment, the receiving module 540 may be configured to perform the operation S240 described above, and is not described herein again.
According to the embodiment of the disclosure, in the case that the first system fails, determining user data associated with the failure in the first system; marking the user data as white list user data, wherein the first system is capable of responding to requests of other users except the white list user data; transferring the white list user data to a second system so as to isolate the white list user data in the first system from faults; in the event of a first system failure fix, white list user data is received from a second system. The method and the device solve the technical problems that in the related art, once the system fails, the normal operation of the whole system is influenced, and the user experience of the system is reduced. The processing method has the advantages that when the system fails, the white list data associated with the failure are subjected to fault isolation and fault recovery based on the white list processing mode, the fact that the operation of the whole system is not affected by the occurring failure is guaranteed, the fault processing efficiency is improved, the influence range of the system failure is reduced, the system user experience is improved, meanwhile, the processing method is written and realized based on the Python scripting language, when the system failure occurs, the deployment is convenient, the operation is convenient and fast, and the data migration efficiency is improved.
According to the embodiment of the disclosure, the second system comprises a temporary service table and a target service table, all initial user data in the first system is transferred from the second system, and all initial user data in the first system is stored in the target service table.
According to an embodiment of the present disclosure, the transfer module 530 may include: the system comprises a transfer submodule, an update submodule and a first modification submodule.
And the transfer submodule is used for transferring the white list user data to the temporary service list.
And the updating submodule is used for updating the initial user data in the target service table which is the same as the main key in the temporary service table into the white list data based on the white list data transferred in the temporary service table.
And the first modification submodule is used for modifying the transaction route of the white list data to the second system so as to carry out fault isolation on the white list user data in the first system.
According to an embodiment of the present disclosure, the receiving module 530 may include: and the clearing submodule and the receiving submodule.
A purge submodule for purging user data associated with the fault in the first system.
And the receiving submodule is used for receiving the white list user data from the second system based on the preset logic rule.
According to an embodiment of the present disclosure, after receiving the white list user data from the second system, the method further includes: transaction routing of the white list user data is modified to the repaired first system.
According to an embodiment of the present disclosure, the determining module 510 may include: and (5) analyzing the submodule.
And the analysis submodule is used for analyzing the transaction log in the first system to obtain user data associated with the fault.
According to an embodiment of the present disclosure, the marking module 520 may include: a second modification submodule and a marking submodule.
A second modification submodule for modifying a state of user data associated with the fault in the first system.
And the marking sub-module is used for marking the modified user data as white list user data.
According to the embodiment of the present disclosure, after marking the user data as white list user data, the method further includes: and controlling business transaction of the white list user data.
According to an embodiment of the present disclosure, any plurality of the determining module 510, the marking module 520, the transferring module 530, and the receiving module 540 may be combined into one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the determining module 510, the marking module 520, the transferring module 530, and the receiving module 540 may be implemented at least in part 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 may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of three implementations of software, hardware, and firmware, or in a suitable combination of any of them. Alternatively, at least one of the determining module 510, the marking module 520, the transferring module 530 and the receiving module 540 may be at least partially implemented as a computer program module, which when executed may perform a corresponding function.
Fig. 6 schematically shows a block diagram of an electronic device adapted to implement a fault handling method according to an embodiment of the present disclosure.
As shown in fig. 6, an 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 section 608 into a Random Access Memory (RAM) 603. Processor 601 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 601 may also include onboard memory for caching purposes. Processor 601 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the disclosure.
In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are stored. The processor 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. The processor 601 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 602 and/or RAM 603. It is to be noted that the program may also be stored in one or more memories other than the ROM 602 and the RAM 603. The processor 601 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in one or more memories.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments 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 the ROM 602 and RAM 603.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the fault handling method provided by the embodiment of the disclosure.
The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 601. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal on a network medium, downloaded and installed through the communication section 609, and/or installed from the removable medium 611. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The computer program, when executed by the processor 601, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.
Claims (12)
1. A fault handling method, comprising:
in the event of a failure of a first system, determining user data in the first system associated with the failure;
tagging the user data as whitelisted user data, wherein the first system is capable of responding to requests by other users in addition to the whitelisted user data;
transferring the white list user data to a second system so as to isolate the white list user data in the first system from faults; and
receiving the whitelist user data from the second system in the event the first system fails to repair.
2. The method of claim 1, wherein the second system comprises a temporary service table and a target service table, all initial user data in the first system is transferred from the second system, and all initial user data in the first system is stored in the target service table;
transferring the whitelist user data to a second system for fault isolation of the whitelist user data in the first system, comprising:
transferring the white list user data to the temporary service table;
updating the initial user data in the target service table which is the same as the primary key in the temporary service table into the white list data based on the white list data transferred in the temporary service table;
modifying a transaction route for the white list data to the second system to facilitate fault isolation of the white list user data in the first system.
3. The method of claim 1, wherein receiving the whitelist user data from the second system in the event the first system fails to repair comprises:
clearing user data associated with the fault in the first system;
receiving the white list user data from the second system based on a preset logic rule.
4. The method of claim 1, further comprising, after said receiving said whitelist user data from said second system:
modifying the transaction route of the white list user data to the repaired first system.
5. The method of claim 1, wherein determining user data associated with the fault in the first system comprises:
analyzing the transaction log in the first system to obtain user data associated with the fault.
6. The method of claim 1, wherein said tagging said user data as whitelisted user data comprises:
modifying a state of user data associated with the fault in the first system;
and marking the modified user data as white list user data.
7. The method of claim 1, further comprising, after said marking said user data as white listed user data:
and controlling the business transaction of the white list user data.
8. The method according to any one of claims 1 to 7, wherein the fault handling method is implemented based on Python scripting language writing.
9. A fault handling device comprising:
the system comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining user data associated with a fault in a first system under the condition that the first system has the fault;
a tagging module configured to tag the user data as white list user data, wherein the first system is capable of responding to requests of other users than the white list user data;
a transferring module, configured to transfer the white list user data to a second system, so as to perform fault isolation on the white list user data in the first system; and
a receiving module, configured to receive the white list user data from the second system when the first system is in a failure recovery state.
10. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-8.
11. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 8.
12. A computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111487776.7A CN114138564B (en) | 2021-12-07 | 2021-12-07 | Fault handling method, processing device, electronic device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111487776.7A CN114138564B (en) | 2021-12-07 | 2021-12-07 | Fault handling method, processing device, electronic device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114138564A true CN114138564A (en) | 2022-03-04 |
| CN114138564B CN114138564B (en) | 2025-06-06 |
Family
ID=80385000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111487776.7A Active CN114138564B (en) | 2021-12-07 | 2021-12-07 | Fault handling method, processing device, electronic device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114138564B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116320014A (en) * | 2023-03-24 | 2023-06-23 | 中国工商银行股份有限公司 | Message scheduling method, device, equipment and medium during parallel period of old and new systems |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN102999587A (en) * | 2011-11-16 | 2013-03-27 | 微软公司 | Arrangement for mirror database across different servers used for failover |
| CN104750757A (en) * | 2013-12-31 | 2015-07-01 | 中国移动通信集团公司 | Data storage method and equipment based on HBase |
| US20160034355A1 (en) * | 2014-08-04 | 2016-02-04 | Microsoft Corporation | Recovering usability of cloud based service from system failure |
-
2021
- 2021-12-07 CN CN202111487776.7A patent/CN114138564B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102999587A (en) * | 2011-11-16 | 2013-03-27 | 微软公司 | Arrangement for mirror database across different servers used for failover |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN104750757A (en) * | 2013-12-31 | 2015-07-01 | 中国移动通信集团公司 | Data storage method and equipment based on HBase |
| US20160034355A1 (en) * | 2014-08-04 | 2016-02-04 | Microsoft Corporation | Recovering usability of cloud based service from system failure |
Non-Patent Citations (1)
| Title |
|---|
| 戴华 等: ""基于CTMO模型的数据库损坏数据隔离技术"", 《计算机学报》, vol. 34, no. 2, 28 February 2011 (2011-02-28), pages 275 - 290 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116320014A (en) * | 2023-03-24 | 2023-06-23 | 中国工商银行股份有限公司 | Message scheduling method, device, equipment and medium during parallel period of old and new systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114138564B (en) | 2025-06-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11449379B2 (en) | Root cause and predictive analyses for technical issues of a computing environment | |
| US9612936B2 (en) | Correlation of source code with system dump information | |
| US8291382B2 (en) | Maintenance assessment management | |
| US8930761B2 (en) | Test case result processing | |
| CN113014445B (en) | Operation and maintenance method, device and platform for server and electronic equipment | |
| US20180005286A1 (en) | Issue resolution utilizing feature mapping | |
| US20100077257A1 (en) | Methods for disaster recoverability testing and validation | |
| CN114205216A (en) | Root cause positioning method and device for micro-service fault, electronic equipment and medium | |
| US20100131472A1 (en) | Detection and utilzation of inter-module dependencies | |
| CN114996265B (en) | Data blood relationship acquisition method, apparatus, device and computer program product | |
| CN110555150A (en) | Data monitoring method, device, equipment and storage medium | |
| CN114138564B (en) | Fault handling method, processing device, electronic device and readable storage medium | |
| CN111884858A (en) | Equipment asset information verification method, device, system and medium | |
| CN110716804A (en) | Method and device for automatically deleting useless resources, storage medium and electronic equipment | |
| CN114637689A (en) | Application evaluation method, device, equipment and storage medium | |
| CN113553462A (en) | Asset information verification method, system and device | |
| CN118152963A (en) | Transaction abnormality detection method, device, electronic equipment and computer storage medium | |
| CN118152293A (en) | Interface testing method, device, electronic equipment and computer readable storage medium | |
| CN116975200A (en) | Methods, devices, equipment and media for controlling the working status of servers | |
| CN117171731A (en) | Rights management method, device, equipment and storage medium | |
| CN118964164A (en) | A code repair method, device, equipment and medium | |
| CN115689561B (en) | U shield test method, device, equipment and medium | |
| CN114077630A (en) | A kind of ETL task execution method, system, device, server and storage medium | |
| CN119449602B (en) | Network connection method, apparatus, device, medium, and program product | |
| CN121326611A (en) | Anomaly handling methods, devices, equipment, media and program products |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |