CN112181699A - Fault isolation method and device and multilayer fault isolation system - Google Patents
Fault isolation method and device and multilayer fault isolation system Download PDFInfo
- Publication number
- CN112181699A CN112181699A CN202011003180.0A CN202011003180A CN112181699A CN 112181699 A CN112181699 A CN 112181699A CN 202011003180 A CN202011003180 A CN 202011003180A CN 112181699 A CN112181699 A CN 112181699A
- Authority
- CN
- China
- Prior art keywords
- transaction
- fault isolation
- statistical
- subsystem
- transaction information
- 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; CALCULATING OR 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a fault isolation method and device and a multilayer fault isolation system, and relates to the field of computers. The fault isolation method comprises the following steps: acquiring cached back-end service URL addresses, and counting the acquired transaction information aiming at each back-end service URL address according to a fault isolation range to obtain the statistical transaction information, wherein the fault isolation range is pre-configured and can be transaction-level fault isolation or system-level fault isolation; and when the statistical transaction information meets the preset conditions, carrying out corresponding fault isolation. The fault isolation method can identify system-level faults and transaction-level faults, reduces transaction failures caused by fault isolation, ensures the effectiveness of overall fault isolation of a multi-layer technical framework of the whole financial system, improves the service success rate of the financial system, and improves user experience.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a fault isolation method and device.
Background
In the financial field, the technical architecture mainly adopts a multi-layer architecture, which comprises a channel layer, an enterprise service bus layer, a product layer, an external connection layer and other multi-layer structures, as shown in fig. 1; the financial system is distributed in each layer of the technical architecture according to the respective system service function, and outbound call calling relations exist among subsystems of each layer to form a transaction link.
Because various types of system faults may occur in the operation process of a subsystem at a certain layer of the financial system, including network faults, application memory exhaustion, failure to provide services, long certain transaction time, high resource usage and the like, the faulty subsystem needs to be identified and isolated from a transaction link, so that the system can be ensured to normally operate.
When a single financial system fails in the operation process, transaction processing of the system is slowed down or failed, and whether the transaction is slowed down or the transaction is failed, corresponding fault isolation processing of a fault subsystem in a multi-layer architecture is very important. Currently, fault isolation mechanisms commonly used in financial systems include cluster high availability designs, HA designs, flow control mechanisms, and the like.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
(1) the cluster high-availability design and the HA design mainly aim at system-level faults and directly isolate fault machines or processes, and the transaction-level faults such as slow transaction, low success rate of single transaction service and the like cannot be finely isolated from fault transaction service;
(2) the flow control mechanism mainly aims at the conditions that the transaction is slow and the transaction success rate is low, the fault of the subsystem cannot be identified and isolated, and a large number of failed transactions can be generated by the flow control mechanism, so that the transaction success rate is low.
Disclosure of Invention
In view of this, embodiments of the present invention provide a fault isolation method and apparatus, which can identify a system-level fault and a transaction-level fault, reduce transaction failures caused by fault isolation, ensure validity of overall fault isolation of a multi-layer technical architecture of a whole financial system, improve a success rate of a financial system service, and improve user experience.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a fault isolation method including:
acquiring a cached back-end service URL address;
according to the fault isolation range, counting the collected transaction information aiming at each back-end service URL address to obtain the statistical transaction information;
and when the statistical transaction information meets the preset conditions, carrying out corresponding fault isolation.
Optionally, the method further comprises configuring the fault isolation range in advance.
Optionally, the method further comprises configuring the fault isolation parameters in advance.
Optionally, before counting the collected transaction information for each back-end service URL address according to the fault isolation range to obtain the statistical transaction information, collecting the transaction information is further included.
Optionally, collecting transaction information comprises: and acquiring a back terminal system, a back-end service URL address, transaction response time, transaction success and failure states and the like of each transaction.
Alternatively, the fault isolation scope may be transaction level fault isolation or system level fault isolation.
Optionally, when the fault isolation scope is transaction-level fault isolation, configuring the fault isolation parameter includes: for a single transaction, a threshold parameter for the transaction and a statistical parameter for the transaction are input.
Optionally, when the fault isolation range is transaction-level fault isolation, the threshold parameter of the transaction includes an upper threshold of response time of the transaction and a lower threshold of transaction success rate of the transaction; the statistical parameters of the transaction comprise the number of statistical units of the transaction and the number of fault isolation units of the transaction.
Optionally, when the fault isolation range is transaction-level fault isolation, counting, according to the fault isolation range and for each backend service URL address, the collected transaction information to obtain the statistical transaction information includes: and circularly counting to obtain the average response time and the transaction success rate in the single transaction counting unit number corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the single transaction counting unit number corresponding to each back-end service URL address.
Optionally, when the fault isolation range is transaction-level fault isolation, when the statistical transaction information satisfies a preset condition, the method includes: the average response time is larger than or equal to the response time upper threshold of the transaction or the transaction success rate is smaller than or equal to the transaction success rate lower threshold of the transaction.
Optionally, when the fault isolation range is transaction-level fault isolation, performing corresponding fault isolation includes: and the back-end service URL address of which the statistical transaction information meets the preset condition is isolated from the transaction by the transaction fault isolation number and then recovered.
Optionally, when the fault isolation range is system-level fault isolation, configuring the fault isolation parameter includes: and inputting a subsystem threshold parameter and a subsystem statistical parameter.
Optionally, when the fault isolation range is system-level fault isolation, the system threshold parameter includes a subsystem response time upper threshold and a subsystem transaction success rate lower threshold; the subsystem statistical parameters comprise the number of subsystem statistical units and the number of subsystem fault isolation units.
Optionally, when the fault isolation range is system-level fault isolation, counting, according to the fault isolation range and for each backend service URL address, the transaction information obtained by counting the collected transaction information includes: and circularly counting to obtain the average response time and the transaction success rate of all transactions in the number of the subsystem statistical units corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the number of the subsystem statistical units corresponding to each back-end service URL address.
Optionally, when the fault isolation range is system-level fault isolation, the statistical transaction information meeting the preset condition includes: the average response time is larger than or equal to the upper limit threshold of the response time of the subsystem or the transaction success rate is smaller than or equal to the lower limit threshold of the transaction success rate of the subsystem.
Optionally, when the fault isolation range is system-level fault isolation, performing corresponding fault isolation includes: and isolating the back-end URL service address of which the statistical transaction information meets the preset condition from all the transactions by the subsystem fault isolation stroke number and then recovering.
According to another aspect of embodiments of the present invention, a fault isolation apparatus is provided.
A fault isolation device comprising:
the URL acquisition module is used for acquiring a cached back-end service URL address;
the statistical module is used for carrying out statistics on the collected transaction information aiming at each back-end service URL address according to the fault isolation range to obtain the statistical transaction information;
and the fault isolation module is used for carrying out corresponding fault isolation when the statistical transaction information meets the preset conditions.
Optionally, the system further comprises a fault isolation range configuration module, configured to configure the fault isolation range in advance;
optionally, the system further comprises a fault isolation parameter configuration module, configured to pre-configure the fault isolation parameter.
Optionally, the system further comprises an acquisition module, configured to acquire transaction information before counting the acquired transaction information for each backend service URL address according to the fault isolation range to obtain the statistical transaction information.
Optionally, collecting transaction information comprises: and acquiring a back terminal system, a back-end service URL address, transaction response time, transaction success and failure states and the like of each transaction.
Alternatively, the fault isolation scope may be transaction level fault isolation or system level fault isolation.
Optionally, when the fault isolation range is transaction-level fault isolation, configuring the fault isolation parameter by the fault isolation parameter configuration module includes: for a single transaction, a threshold parameter for the transaction and a statistical parameter for the transaction are input.
Optionally, when the fault isolation range is transaction-level fault isolation, the threshold parameter of the transaction includes an upper threshold of response time of the transaction and a lower threshold of transaction success rate of the transaction; the statistical parameters of the transaction comprise the number of statistical units of the transaction and the number of fault isolation units of the transaction.
Optionally, when the fault isolation range is transaction-level fault isolation, the counting module performs, according to the fault isolation range and for each back-end service URL address, counting the collected transaction information to obtain the statistical transaction information, where the counting includes: and circularly counting to obtain the average response time and the transaction success rate in the single transaction counting unit number corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the single transaction counting unit number corresponding to each back-end service URL address.
Optionally, when the fault isolation range is transaction-level fault isolation, the statistical transaction information meeting the preset condition includes: the average response time is larger than or equal to the response time upper threshold of the transaction or the transaction success rate is smaller than or equal to the transaction success rate lower threshold of the transaction.
Optionally, when the fault isolation range is transaction-level fault isolation, the performing, by the fault isolation module, corresponding fault isolation includes: and the transaction is recovered after isolating the fault isolation stroke number of the transaction by the back-end service URL address of which the statistical transaction information meets the preset condition.
Optionally, when the fault isolation range is system-level fault isolation, configuring the fault isolation parameter by a fault isolation parameter includes: and inputting a subsystem threshold parameter and a subsystem statistical parameter.
Optionally, when the fault isolation range is system-level fault isolation, the subsystem threshold parameter includes a subsystem response time upper threshold and a subsystem transaction success rate lower threshold; the subsystem statistical parameters comprise the number of subsystem statistical units and the number of subsystem fault isolation units.
Optionally, when the fault isolation range is system-level fault isolation, the statistics module performs statistics on the transaction information for each back-end service URL address according to the fault isolation range, and obtaining the statistical transaction information includes: and circularly counting to obtain the average response time and the transaction success rate of all transactions in the number of the subsystem statistical units corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the number of the subsystem statistical units corresponding to each back-end service URL address.
Optionally, when the fault isolation range is system-level fault isolation, the statistical transaction information meeting the preset condition includes: the average response time is larger than or equal to the upper limit threshold of the response time of the subsystem or the transaction success rate is smaller than or equal to the lower limit threshold of the transaction success rate of the subsystem.
Optionally, when the fault isolation range is system-level fault isolation, the performing, by the fault isolation module, corresponding fault isolation includes: and isolating the back-end URL service address of which the statistical transaction information meets the preset condition from all the transactions by the subsystem fault isolation stroke number and then recovering.
According to another aspect of embodiments of the present invention, a multi-layer fault isolation system is provided.
A multi-layer fault isolation system comprising a plurality of layers of subsystems, each layer of subsystems having a fault isolation device disposed therein for fault identification and isolation of a rear terminal system, the fault isolation device comprising:
the URL acquisition module is used for acquiring a cached back-end service URL address;
the statistical module is used for collecting transaction information before the collected transaction information is counted for each back-end service URL address according to the fault isolation range to obtain the statistical transaction information;
and the fault isolation module is used for carrying out corresponding fault isolation when the statistical transaction information meets the preset conditions.
Optionally, the system further comprises a fault isolation range configuration module, configured to configure the fault isolation range in advance;
optionally, the system further comprises a fault isolation parameter configuration module, configured to pre-configure the fault isolation parameter.
Optionally, the system further includes an acquisition module, configured to acquire transaction information before counting the acquired transaction information for each backend service URL address according to the fault isolation range to obtain the statistical transaction information.
Optionally, collecting transaction information comprises: and acquiring a back terminal system, a back-end service URL address, transaction response time, transaction success and failure states and the like of each transaction.
Alternatively, the fault isolation scope may be transaction level fault isolation or system level fault isolation.
Optionally, when the fault isolation range is transaction-level fault isolation, configuring the fault isolation parameter by the fault isolation parameter configuration module includes: for a single transaction, a threshold parameter for the transaction and a statistical parameter for the transaction are input.
Optionally, when the fault isolation range is transaction-level fault isolation, the threshold parameter of the transaction includes an upper threshold of response time of the transaction and a lower threshold of transaction success rate of the transaction; the statistical parameters of the transaction comprise the number of statistical units of the transaction and the number of fault isolation units of the transaction.
Optionally, when the fault isolation range is transaction-level fault isolation, the counting module performs, according to the fault isolation range and for each back-end service URL address, counting the collected transaction information to obtain the statistical transaction information, where the counting includes: and circularly counting to obtain the average response time and the transaction success rate in the single transaction counting unit number corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the single transaction counting unit number corresponding to each back-end service URL address.
Optionally, when the fault isolation range is transaction-level fault isolation, the statistical transaction information meeting the preset condition includes: the average response time is larger than or equal to the response time upper threshold of the transaction or the transaction success rate is smaller than or equal to the transaction success rate lower threshold of the transaction.
Optionally, when the fault isolation range is transaction-level fault isolation, the performing, by the fault isolation module, corresponding fault isolation includes: and the transaction is recovered after isolating the fault isolation stroke number of the transaction by the back-end service URL address of which the statistical transaction information meets the preset condition.
Optionally, when the fault isolation range is system-level fault isolation, configuring the fault isolation parameter by a fault isolation parameter includes: and inputting a subsystem threshold parameter and a subsystem statistical parameter.
Optionally, when the fault isolation range is system-level fault isolation, the subsystem threshold parameter includes a subsystem response time upper threshold and a subsystem transaction success rate lower threshold; the subsystem statistical parameters comprise the number of subsystem statistical units and the number of subsystem fault isolation units.
Optionally, when the fault isolation range is system-level fault isolation, the counting module performs, according to the fault isolation range and for each back-end service URL address, counting the collected transaction information to obtain the statistical transaction information, where the counting includes: and circularly counting to obtain the average response time and the transaction success rate of all transactions in the number of the subsystem statistical units corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the number of the subsystem statistical units corresponding to each back-end service URL address.
Optionally, when the fault isolation range is system-level fault isolation, the statistical transaction information meeting the preset condition includes: the average response time is larger than or equal to the upper limit threshold of the response time of the subsystem or the transaction success rate is smaller than or equal to the lower limit threshold of the transaction success rate of the subsystem.
Optionally, when the fault isolation range is system-level fault isolation, the performing, by the fault isolation module, corresponding fault isolation includes: and isolating the back-end URL service address of which the statistical transaction information meets the preset condition from all the transactions by the subsystem fault isolation stroke number and then recovering.
According to yet another aspect of an embodiment of the present invention, an electronic device is provided.
An electronic device, comprising: one or more processors; a memory for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement the fault isolation method provided by the present invention.
According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.
A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the fault isolation method provided by the invention.
One embodiment of the above invention has the following advantages or benefits: a fault isolation range is configured in advance, the fault isolation range can be selected from transaction-level fault isolation or system-level fault isolation, and fault isolation parameters are configured according to the configured fault isolation range, namely aiming at the transaction-level fault isolation or the system-level fault isolation respectively; collecting information of a rear terminal system, a service URL address, transaction response time, a transaction success and failure state and the like; and aiming at transaction-level fault isolation or system-level fault isolation, carrying out cyclic statistics to obtain the average response time and transaction success rate in the single transaction statistical unit number corresponding to each back-end service URL address, or carrying out cyclic statistics to obtain the average response time and transaction success rate of all transactions in the subsystem statistical unit number corresponding to each back-end service URL address, comparing the average response time and transaction success rate with corresponding threshold values, and carrying out corresponding fault isolation when preset conditions of fault isolation are met. The transaction fault isolation method has the advantages that refined fault isolation can be realized, system-level fault isolation can be realized, transaction failures caused by fault isolation are reduced, a large number of transactions are guaranteed to run in normal service, and the transaction success rate under the fault condition is improved.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic diagram of the main steps of a fault isolation method according to an embodiment of the present invention.
FIG. 2 is a schematic illustration of a flow of a fault isolation method according to an embodiment of the invention;
FIG. 3 is a schematic diagram of the main modules of a fault isolation device according to an embodiment of the present invention;
FIG. 4 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 5 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
According to an aspect of an embodiment of the present invention, there is provided a fault isolation method.
Fig. 1 is a schematic diagram of the main steps of a fault isolation method according to a first embodiment of the present invention.
The invention describes a fault isolation method by taking a financial system as an example.
As shown in fig. 1, the fault isolation method according to the first embodiment of the present invention mainly includes the following steps:
step S101: acquiring a cached back-end service URL address;
step S102: according to the fault isolation range, counting the collected transaction information aiming at each back-end service URL address to obtain the statistical transaction information;
the fault isolation scope can be input by a user in advance, and can be transaction-level fault isolation or system-level fault isolation.
The system level fault is a subsystem level fault, and specifically can be a machine level fault, a network level fault and a process level fault.
Before counting the collected transaction information to obtain the statistical transaction information according to the fault isolation range and aiming at each back-end service URL address, the method also comprises the step of judging whether the fault isolation range is transaction-level fault isolation or system-level fault isolation.
The transaction information may be an outbound transaction code, a back-end terminal system, a back-end service URL address, transaction response time, a transaction success or failure status, and the like of each transaction collected from a transaction log or a transaction flow meter.
The statistics of the collected transaction information can be performed respectively for a system level and a transaction level, and the transaction response time and the transaction success and failure states are counted to obtain the statistical transaction information. The statistical trade information may be average response time and trade success rate.
When the fault isolation range is transaction-level fault isolation, counting the collected transaction information for each back-end service URL address, and obtaining the statistical transaction information comprises: and circularly counting to obtain the average response time and the transaction success rate in the single transaction counting unit number corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the single transaction counting unit number corresponding to each back-end service URL address.
When the fault isolation range is system-level fault isolation, counting the collected transaction information aiming at each back-end service URL address, and obtaining the statistical transaction information comprises the following steps: and circularly counting to obtain the average response time and the transaction success rate of all transactions in the number of the subsystem statistical units corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the number of the subsystem statistical units corresponding to each back-end service URL address.
Step S103: and when the statistical transaction information meets the preset conditions, carrying out corresponding fault isolation.
The statistical transaction information meeting the preset condition means that the average response time is greater than or equal to the response time upper limit threshold or the transaction success rate is less than or equal to the transaction success rate lower limit threshold.
The response time upper threshold and the transaction success rate lower threshold may be preset.
The response time upper threshold may be the response time upper threshold for the transaction for transaction-level fault isolation or may be a subsystem response time upper threshold for system-level fault isolation.
The transaction success rate lower threshold may be a transaction success rate lower threshold for the transaction for transaction-level fault isolation, or may be a subsystem transaction success rate for system-level fault isolation.
And performing corresponding fault isolation, namely isolating the back-end service URL address meeting the preset condition from the fault isolation number of the transaction and then recovering.
Specifically, performing the corresponding fault isolation includes: when the fault isolation range is transaction-level fault isolation, the transaction is recovered after isolating the back-end service URL address of which the statistical transaction information meets the preset condition from the fault isolation number of the transaction; and when the fault isolation range is system-level fault isolation, all transactions of the back-end subsystem recover after isolating the back-end URL service addresses of which the statistical transaction information meets the preset conditions from the subsystem fault isolation stroke number.
As shown in fig. 2, the schematic diagram of the flow of the fault isolation method of the present embodiment includes steps S201 to S212 as follows.
Step S201: configuring an isolation range;
step S202: judging whether the fault isolation range is transaction-level fault isolation or system-level fault isolation, and entering step S203 when the fault isolation range is transaction-level fault isolation; when the fault isolation range is system-level fault isolation, the step S208 is entered;
step S203: setting transaction-level threshold parameters and statistical parameters;
step S204: acquiring a cached back-end service URL address;
step S205: collecting and counting transaction information;
step S206: judging a fault;
step S207: performing transaction-level fault isolation, and returning to step S205;
step S208: setting a system level threshold parameter and a statistical parameter;
step S209: acquiring a cached back-end service URL address;
step S210: collecting and counting transaction information;
step S211: judging a fault;
step S212: performing system-level fault isolation and returning to step S210;
in the above flow, the sequence of step S203 and step S204 may be exchanged, and the sequence of step S208 and step S209 may be exchanged.
In step S203, the transaction level threshold parameter may be set as an upper threshold Tra of the average response time of transaction a and a lower threshold Tsa of the transaction success rate of transaction a for single transaction a; setting statistical parameters may include inputting a statistical unit number of strokes (S strokes) and a fault isolation number of strokes (Ka strokes);
in step S208, the system level threshold parameter may be set as an upper threshold Tr of average response time in the subsystem and a lower threshold Ts of transaction success rate in the subsystem for the subsystem (for example, a0151 subsystem); setting statistical parameters may include inputting a statistical unit number of strokes (S strokes) and a fault isolation number of strokes (K strokes);
counting the number of units (S pens) to show that S pens are counted each time, and counting the number of fault isolation pens (K pens) to show that the fault transaction service and the subsystem are isolated for K times under the condition that the condition is not met;
in step S204, the cached URL address of the backend service may be obtained by obtaining a URL service address of a backend subsystem corresponding to the single transaction and downloading the URL service address to the local, for example, as shown in the following table:
in Table 1, transaction A belongs to the A0138 subsystem, and http:// IP1:8001/irl and http:// IP2:8001/irl are service access addresses of the A0138 subsystem.
In step S209, the cached back-end service URL address may be obtained as a back-end subsystem URL service address corresponding to the acquisition single transaction and downloaded locally, for example, as shown in the following table:
in step S205 and step S210, the collecting transaction information includes: and collecting information such as an outbound transaction code, a rear terminal system, a rear-end service URL (uniform resource locator) address, transaction response time, a transaction success and failure state and the like of each transaction from a transaction log or a transaction flow meter.
In step S205, the statistical transaction information is: and circularly counting to obtain the average response time and the transaction success rate in the S transactions corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the single transaction counting unit stroke number (namely the S transactions) corresponding to each back-end service URL address.
Specific examples can be shown in the following table:
in step S210, the statistical transaction information is: according to the obtained subsystem corresponding to each back-end URL service address, such as an A0151 subsystem, counting the transaction response time and the transaction failure success state of each transaction in the unit stroke number (namely S strokes), and circularly counting to obtain the average response time and the transaction success rate of all transactions in the S strokes corresponding to each back-end URL service address.
Specific examples can be shown in the following table:
step S206 includes: for each back-end service URL address, judging whether the average response time of the transaction is greater than or equal to the response time upper threshold value or not, and judging whether the transaction success rate of the transaction is less than or equal to the transaction success rate lower threshold value or not, if a certain back-end service URL address of the transaction meets the condition that the average response time is greater than or equal to the response time upper threshold value or the transaction success rate is less than or equal to the transaction success rate lower threshold value, judging that the back-end URL service corresponding to the back-end service URL address has a fault, wherein specific examples are shown in the following table:
for the backend service URL address http:// IP2:8001/irl, the average response time of the current S transactions is 150ms and is greater than Tra, and the success rate of the current S transactions is 95% and is less than Tsa, the backend service URL address of transaction A is judged to be the failure of the backend URL service of http:// IP2: 8001/irl.
Step S211 includes: for each back-end service URL address, judging whether the average response time of the subsystem is greater than or equal to the upper threshold of the response time of the subsystem and whether the transaction success rate of the subsystem is less than or equal to the lower threshold of the transaction success rate of the subsystem, if a certain back-end service URL address of the subsystem meets the condition that the average response time is greater than or equal to the upper threshold of the response time of the subsystem or the transaction success rate of the subsystem is less than or equal to the lower threshold of the transaction success rate of the subsystem, judging that the back-end URL service corresponding to the back-end service URL address has a fault, wherein specific examples are shown in:
for the backend service URL address http:// IP4:8001/irl, the average response time of the current S transactions is 2000ms and is larger than Tr, and the backend URL service of the subsystem A0151 with the backend service URL address http:// IP4:8001/irl is judged to have a fault.
In steps S207 and S212, corresponding fault isolation is performed, that is, the service URL address is updated, specifically, the service URL address is updated as shown in the following table:
in step S207, the transaction A is recovered after isolating the http:// IP2:8001/irl service address from the Ka pen, and in step S212, all transactions in the A0151 system are recovered after isolating the http:// IP4:8001/irl service address from the K pen.
In this embodiment, a threshold parameter and a statistical parameter may be set according to an input fault isolation range, that is, a transaction-level fault isolation range or a system-level fault isolation range, to obtain a cached service URL address, and correspondingly count transaction information, and perform corresponding fault isolation when the obtained statistical transaction information meets a preset condition. The method can cover transaction-level faults and system-level faults, and improve the transaction success rate under the fault condition.
According to a second aspect of embodiments of the present invention, a fault isolation device is provided.
Fig. 3 is a schematic diagram of the main modules of a fault isolation device according to an embodiment of the invention.
As shown in fig. 3, a fault isolation apparatus 300 of an embodiment of the present invention includes:
a URL obtaining module 303, configured to obtain a cached backend service URL address;
a counting module 305, configured to count the collected transaction information according to a preconfigured fault isolation range and for each backend service URL address to obtain the counted transaction information;
and the fault isolation module 306 is configured to perform corresponding fault isolation when the statistical transaction information meets a preset condition.
Optionally, the system further includes a fault isolation range configuration module 301, configured to configure a fault isolation range in advance;
optionally, a fault isolation parameter configuration module 302 is further included for pre-configuring fault isolation parameters.
Optionally, the system further includes an acquisition module 304, configured to acquire transaction information before counting the acquired transaction information for each backend service URL address according to the fault isolation range to obtain the statistical transaction information.
Optionally, collecting transaction information comprises: and acquiring a back terminal system, a back-end service URL address, transaction response time, transaction success and failure states and the like of each transaction.
Alternatively, the fault isolation scope may be transaction level fault isolation or system level fault isolation.
Optionally, when the fault isolation range is transaction-level fault isolation, configuring the fault isolation parameter by the fault isolation parameter configuration module includes: for a single transaction, a threshold parameter for the transaction and a statistical parameter for the transaction are input.
Optionally, when the fault isolation range is transaction-level fault isolation, the threshold parameter of the transaction includes an upper threshold of response time of the transaction and a lower threshold of transaction success rate of the transaction; the statistical parameters of the transaction comprise the number of statistical units of the transaction and the number of fault isolation units of the transaction.
Optionally, when the fault isolation range is a transaction-level fault isolation range, the statistics module 305 performs statistics on the transaction information for each back-end service URL address according to the fault isolation range, and obtaining the statistical transaction information includes: and circularly counting to obtain the average response time and the transaction success rate in the single transaction counting unit number corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the single transaction counting unit number corresponding to each back-end service URL address.
Optionally, when the fault isolation range is transaction-level fault isolation, the statistical transaction information meeting the preset condition includes: the average response time is larger than or equal to the response time upper threshold of the transaction or the transaction success rate is smaller than or equal to the transaction success rate lower threshold of the transaction.
Optionally, when the fault isolation range is transaction-level fault isolation, the fault isolation module 306 performs corresponding fault isolation, including: and the transaction is recovered after isolating the fault isolation stroke number of the transaction by the back-end service URL address of which the statistical transaction information meets the preset condition.
Optionally, when the fault isolation range is system-level fault isolation, configuring the fault isolation parameter by a fault isolation parameter includes: and inputting a subsystem threshold parameter and a subsystem statistical parameter.
Optionally, when the fault isolation range is system-level fault isolation, the subsystem threshold parameter includes a subsystem response time upper threshold and a subsystem transaction success rate lower threshold; the subsystem statistical parameters comprise the number of subsystem statistical units and the number of subsystem fault isolation units.
Optionally, when the fault isolation range is system-level fault isolation, the counting module 305 counts the collected transaction information according to the fault isolation range and for each back-end service URL address, and obtains the statistical transaction information includes: and circularly counting to obtain the average response time and the transaction success rate of all transactions in the number of the subsystem statistical units corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the number of the subsystem statistical units corresponding to each back-end service URL address.
Optionally, when the fault isolation range is system-level fault isolation, the statistical transaction information meeting the preset condition includes: the average response time is larger than or equal to the upper limit threshold of the response time of the subsystem or the transaction success rate is smaller than or equal to the lower limit threshold of the transaction success rate of the subsystem.
Optionally, when the fault isolation range is system-level fault isolation, the performing, by the fault isolation module 306, corresponding fault isolation includes: and isolating the back-end URL service address of which the statistical transaction information meets the preset condition from all the transactions by the subsystem fault isolation stroke number and then recovering.
According to a third aspect of the present invention there is provided a multi-layer fault isolation system comprising: and each layer of subsystem is provided with a fault isolation device for identifying and isolating faults of the rear terminal system.
According to a fourth aspect of embodiments of the present invention, there is provided an electronic apparatus, including:
one or more processors;
a memory 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 are caused to implement the method provided by the first aspect of the embodiments of the present invention.
According to a fourth aspect of the embodiments of the present invention, there is provided a computer-readable medium on which a computer program is stored, wherein the program is configured to implement the method provided by the first aspect of the embodiments of the present invention when executed by a processor.
Fig. 4 illustrates an exemplary system architecture 400 to which the fault isolation method or fault isolation apparatus of embodiments of the invention may be applied.
As shown in fig. 4, the system architecture 400 may include terminal devices 401, 402, 403, a network 404, and a server 405. The network 402 serves as a medium for providing communication links between the terminal devices 401, 402, 403 and the server 405. Network 404 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
The communication with the server 405 may be performed via a network 404 through terminal devices 401, 402, 403 provided with fault isolation means.
The terminal devices 401, 402, 403 may be various electronic devices including, but not limited to, smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 403 may be a server that provides various services, such as a background management server (for example only) that provides support for isolating backend services that determine failures. The background management server can recover the back-end service URL which is judged to have a fault after isolating for a certain number of times.
It should be noted that the fault isolation method provided by the embodiment of the present invention may be executed by the terminal devices 401, 402, and 403, and accordingly, the fault isolation apparatus in each layer of subsystem may be disposed in the terminal devices 401, 402, and 403.
It should be understood that the number of terminal devices, networks, and servers in fig. 4 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 5, shown is a block diagram of a computer system 500 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU)501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the system 500 are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 501.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, 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), an optical fiber, 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 invention, 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. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
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 invention. 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.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprising: the device comprises a fault isolation range setting module, a fault isolation parameter setting module, a URL (uniform resource locator) acquisition module, an acquisition module, a statistical module and a fault isolation module. Where the names of these modules do not in some cases constitute a limitation of the module itself, for example, a statistics module may also be described as a "statistics module of transaction information according to fault isolation scope".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: according to the fault isolation range, counting the collected transaction information aiming at each back-end service URL address to obtain the statistical transaction information; and when the statistical transaction information meets the preset conditions, carrying out corresponding fault isolation.
According to the technical scheme of the embodiment of the invention, the cached back-end service URL addresses are obtained by pre-configuring the fault isolation range, the collected transaction information is counted aiming at each back-end service URL address according to the fault isolation range, and corresponding fault isolation is carried out when the obtained counted transaction information meets the preset condition. Due to the fact that the fault isolation range is set, transaction-level fault isolation or system-level fault isolation can be selected, system-level faults and transaction-level faults can be covered, transaction failures caused by fault isolation are reduced, effectiveness of overall fault isolation of the multi-layer technical framework of the whole financial system is guaranteed, service success rate of the financial system is improved, and user experience is improved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (21)
1. A method of fault isolation, the method comprising:
acquiring a cached back-end service URL address;
according to the fault isolation range, counting the collected transaction information aiming at each back-end service URL address to obtain the statistical transaction information;
and correspondingly isolating the fault when the statistical transaction information meets the preset condition.
2. The method of claim 1, further comprising pre-configuring a fault isolation scope.
3. The method of claim 2, further comprising pre-configuring fault isolation parameters.
4. The method of claim 3, wherein collecting the transaction information further comprises collecting the transaction information before counting the collected transaction information for each service URL address according to a fault isolation scope to obtain the statistical transaction information.
5. The method of claim 4, wherein collecting the transaction information comprises: and acquiring a back terminal system, a back-end service URL address, transaction response time, transaction success and failure states and the like of each transaction.
6. The method of claim 5, wherein the fault isolation scope is transaction-level fault isolation.
7. The method of claim 6, wherein pre-configuring the fault isolation parameters comprises: for a single transaction, a threshold parameter for the transaction and a statistical parameter for the transaction are input.
8. The method of claim 7, wherein the threshold parameters for a transaction include an upper response time threshold for the transaction and a lower transaction success rate threshold for the transaction; the statistical parameters of the transaction comprise the number of statistical units of the transaction and the number of fault isolation units of the transaction.
9. The method of claim 8, wherein counting the transaction information for each backend service URL address according to the fault isolation scope to obtain statistical transaction information comprises: and circularly counting to obtain the average response time and the transaction success rate in the single transaction counting unit number corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the single transaction counting unit number corresponding to each back-end service URL address.
10. The method of claim 9, wherein the statistical transaction information satisfying a preset condition comprises: the average response time is larger than or equal to the response time upper threshold of the transaction or the transaction success rate is smaller than or equal to the transaction success rate lower threshold of the transaction.
11. The method of claim 10, wherein performing the fault isolation comprises: and the back-end service URL address of which the statistical transaction information meets the preset condition is isolated from the transaction by the transaction fault isolation number and then recovered.
12. The method of claim 5, wherein the fault isolation scope is system level fault isolation.
13. The method of claim 12, wherein pre-configuring the fault isolation parameters comprises: and inputting a subsystem threshold parameter and a subsystem statistical parameter.
14. The method of claim 13, wherein the system threshold parameters include an upper subsystem response time threshold and a lower subsystem transaction success rate threshold; the subsystem statistical parameters comprise the number of subsystem statistical units and the number of subsystem fault isolation units.
15. The method of claim 14, wherein the transaction information is counted for each backend service URL address according to the fault isolation scope, and obtaining statistical transaction information comprises: and circularly counting to obtain the average response time and the transaction success rate of all transactions in the number of the subsystem statistical units corresponding to each back-end service URL address according to the acquired transaction response time and the transaction failure success state of each transaction in the number of the subsystem statistical units corresponding to each back-end service URL address.
16. The method of claim 15, wherein the statistical transaction information satisfying a preset condition comprises: the average response time is larger than or equal to the upper limit threshold of the response time of the subsystem or the transaction success rate is smaller than or equal to the lower limit threshold of the transaction success rate of the subsystem.
17. The method of claim 16, wherein performing the fault isolation comprises: and isolating the back-end URL service addresses of which the statistical transaction information meets the preset conditions from the subsystem fault isolation stroke number by all transactions in the back-end subsystem, and then recovering.
18. A fault isolation device comprising:
the URL acquisition module is used for acquiring a cached back-end service URL address;
the statistical module is used for carrying out statistics on the collected transaction information aiming at each back-end service URL address according to the fault isolation range to obtain the statistical transaction information;
and the fault isolation module is used for carrying out corresponding fault isolation when the statistical transaction information meets the preset conditions.
19. A multi-tier fault isolation system comprising a plurality of tiers of subsystems, each tier of subsystems having disposed therein a fault isolation apparatus as claimed in claim 18 for fault identification and isolation of a rear end sub-system.
20. An electronic device, comprising
One or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-17.
21. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-17.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011003180.0A CN112181699B (en) | 2020-09-22 | 2020-09-22 | Fault isolation method and device and multilayer fault isolation system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011003180.0A CN112181699B (en) | 2020-09-22 | 2020-09-22 | Fault isolation method and device and multilayer fault isolation system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112181699A true CN112181699A (en) | 2021-01-05 |
| CN112181699B CN112181699B (en) | 2023-01-24 |
Family
ID=73957083
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011003180.0A Active CN112181699B (en) | 2020-09-22 | 2020-09-22 | Fault isolation method and device and multilayer fault isolation system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112181699B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080209273A1 (en) * | 2007-02-28 | 2008-08-28 | Microsoft Corporation | Detect User-Perceived Faults Using Packet Traces in Enterprise Networks |
| CN104408656A (en) * | 2014-10-29 | 2015-03-11 | 中国建设银行股份有限公司 | Method and system for dynamic adjusting flow control threshold |
| CA3117136A1 (en) * | 2019-07-25 | 2020-01-28 | Intuit Inc. | Detecting life events by applying anomaly detection methods to transaction data |
| CN111192130A (en) * | 2019-12-11 | 2020-05-22 | 中国建设银行股份有限公司 | Method, system, device and storage medium for determining fault source in transaction monitoring |
-
2020
- 2020-09-22 CN CN202011003180.0A patent/CN112181699B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080209273A1 (en) * | 2007-02-28 | 2008-08-28 | Microsoft Corporation | Detect User-Perceived Faults Using Packet Traces in Enterprise Networks |
| CN104408656A (en) * | 2014-10-29 | 2015-03-11 | 中国建设银行股份有限公司 | Method and system for dynamic adjusting flow control threshold |
| CA3117136A1 (en) * | 2019-07-25 | 2020-01-28 | Intuit Inc. | Detecting life events by applying anomaly detection methods to transaction data |
| CN111192130A (en) * | 2019-12-11 | 2020-05-22 | 中国建设银行股份有限公司 | Method, system, device and storage medium for determining fault source in transaction monitoring |
Non-Patent Citations (1)
| Title |
|---|
| 张晓丹: "面向业务应用交易的IT运维监控系统建设思路", 《中国金融电脑》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112181699B (en) | 2023-01-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10560465B2 (en) | Real time anomaly detection for data streams | |
| KR20220062101A (en) | Information transmission method, apparatus, readable medium and electronic device | |
| US8898520B1 (en) | Method of assessing restart approach to minimize recovery time | |
| CN109936613B (en) | Disaster recovery method and device applied to server | |
| CN116627333A (en) | Log caching method and device, electronic equipment and computer readable storage medium | |
| CN111177513A (en) | Method and device for determining abnormal access address, electronic equipment and storage medium | |
| CN112905930A (en) | Interface request retransmission method and device | |
| CN112181699B (en) | Fault isolation method and device and multilayer fault isolation system | |
| CN113760522A (en) | Task processing method and device | |
| CN108959285B (en) | Database main key acquisition method and device, storage medium and electronic equipment | |
| US11494239B2 (en) | Method for allocating computing resources, electronic device, and computer program product | |
| CN115525411A (en) | Method, device, electronic equipment and computer readable medium for processing service request | |
| CN113778977A (en) | Data processing method and data processing device | |
| CN114374657A (en) | Data processing method and device | |
| CN114049065A (en) | Data processing method, device and system | |
| CN114064403A (en) | Task delay analysis processing method and device | |
| CN113779122A (en) | Method and apparatus for exporting data | |
| CN113742355A (en) | Method, device, equipment and computer readable medium for updating inventory | |
| CN112306371A (en) | Method, apparatus and computer program product for storage management | |
| CN111290927A (en) | Data monitoring method and device | |
| CN114553894B (en) | Data synchronization method, device, system and storage medium | |
| CN110632863B (en) | Unmanned aerial vehicle data transmission method and device | |
| CN112181700A (en) | Fault transaction isolation method and device | |
| CN113760469A (en) | Distributed computing method and device | |
| CN113760982A (en) | Data processing method and device |
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 |