CN111258790A - Anomaly compensation method and device - Google Patents
Anomaly compensation method and device Download PDFInfo
- Publication number
- CN111258790A CN111258790A CN201811465386.8A CN201811465386A CN111258790A CN 111258790 A CN111258790 A CN 111258790A CN 201811465386 A CN201811465386 A CN 201811465386A CN 111258790 A CN111258790 A CN 111258790A
- Authority
- CN
- China
- Prior art keywords
- task
- compensation
- abnormal
- execution
- application server
- 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
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000002159 abnormal effect Effects 0.000 claims abstract description 182
- 238000012545 processing Methods 0.000 claims abstract description 25
- 238000012544 monitoring process Methods 0.000 claims description 18
- 239000000725 suspension Substances 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 9
- 238000011161 development Methods 0.000 abstract description 8
- 230000005856 abnormality Effects 0.000 description 41
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 13
- 230000004044 response Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000008901 benefit Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/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/0715—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 system implementing multitasking
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses an anomaly compensation method and device, and relates to the technical field of computers. Wherein, the method comprises the following steps: receiving an abnormal compensation task submitted by at least one application server, and storing the abnormal compensation task to a database; respectively starting corresponding execution threads for the abnormal compensation tasks under each application server, capturing the abnormal compensation tasks from the database based on the execution threads, and executing the abnormal compensation tasks in an RPC calling mode under the condition that the abnormal compensation tasks meet preset execution conditions. Through the steps, the abnormity of each application server can be uniformly compensated, the decoupling of the abnormity compensation logic and the application server business logic is realized, the development cost is reduced, the maintainability of the abnormity compensation logic is improved, and the abnormity compensation processing logic can be optimized.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an anomaly compensation method and device.
Background
The proper functioning of the application system (or application server) depends on the various components (such as Mysql, MQ, Redis) and the various services provided by other application systems. During the operation of the application server, various abnormal situations may occur. For example, in application systems, there are often scenarios where critical process nodes asynchronously notify downstream systems through MQs. In such a scenario, an exception may occur where the MQ message fails to be sent.
When an application system is in an abnormal condition, the following exception handling schemes are mainly used in the prior art: the scheme 1 is that the application system does not carry out any treatment on abnormal conditions; according to the scheme 2, an application system only captures the abnormity and prints the information such as the abnormity type in a log mode, but does not compensate the abnormity; and 3, the application system performs local persistent storage on the abnormal information and then performs timing processing on the abnormal information according to an abnormal compensation processing logic designed by the application system.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
first, scheme 1 does not deal with any exception, which may affect the integrity and accuracy of the whole service flow of the system, and the overall effect of the exception on the system cannot be estimated.
Secondly, the scheme 2 is only to print the abnormal information, but not to compensate the abnormal information, which affects the execution of the business logic of the downstream system and cannot perform manual intervention on the abnormal information in time.
Third, in the case of the scheme 3, although the abnormality is compensated, there are the following problems: 1. because each application system needs to design an exception compensation processing logic, the exception compensation processing logic is coupled with the normal service logic of the system, so that the maintainability of the exception compensation processing logic is poor, and the development cost is increased when each system develops the exception compensation logic; 2. the exception compensation processing logic is not reasonable. For example, if downstream system services are not available all the time, performing an exception compensation task retry all the time may result in an application server being overloaded, resulting in a decrease in the concurrency capability of other traffic of the system.
Disclosure of Invention
In view of this, the present invention provides an anomaly compensation method and apparatus, which can not only perform compensation uniformly for anomalies of each application server, implement decoupling of an anomaly compensation logic and an application server service logic, reduce development cost, improve maintainability of the anomaly compensation logic, but also optimize an anomaly compensation processing logic.
To achieve the above object, according to one aspect of the present invention, there is provided an abnormality compensation method.
The abnormality compensation method of the present invention includes: receiving an abnormal compensation task submitted by at least one application server, and storing the abnormal compensation task to a database; respectively starting corresponding execution threads for the abnormal compensation tasks under each application server, capturing the abnormal compensation tasks from the database based on the execution threads, and executing the abnormal compensation tasks in an RPC calling mode under the condition that the abnormal compensation tasks meet preset execution conditions.
Optionally, the method further comprises: and under the condition that the abnormal compensation task does not meet the preset execution condition, capturing the next abnormal compensation task from the database based on the execution thread.
Optionally, the preset execution condition includes: the task state of the abnormal compensation task is a creation state, and/or the current time meets an execution time strategy of the abnormal compensation task; wherein the creation status indicates that the exception compensation task has not been successfully executed and that the number of execution failures is less than or equal to a task suspension threshold.
Optionally, the method further comprises: after the step of executing the abnormal compensation task in an RPC calling mode, if the abnormal compensation task fails to be executed, updating the execution failure times of the abnormal compensation task; and updating the task state of the exception compensation task to a suspended state when the updated execution failure times are greater than a task suspended threshold; and under the condition that the execution of the abnormity compensation task is successful, updating the task state of the abnormity compensation task to be a success state.
Optionally, the method further comprises: before the step of storing the abnormal compensation task into a database is executed, confirming that the database has application access information matched with an application server identifier carried by the abnormal compensation task, and/or confirming that the abnormal compensation task is not repeatedly submitted; wherein the application access information comprises: and identification of the accessed application server.
Optionally, the method further comprises: monitoring the execution condition of the abnormal compensation task in the database; triggering alarm operation under the condition that the total number of the abnormal compensation tasks under the same application server side or the total number of the abnormal compensation tasks under the same task type exceeds a first threshold value; and/or triggering alarm operation under the condition that the total number of the abnormal compensation tasks in the suspended state under the same application server side or the total number of the abnormal compensation tasks in the suspended state under the same task type exceeds a second threshold value.
Optionally, the method further comprises: and configuring the application access information and storing the application access information to the database.
To achieve the above object, according to another aspect of the present invention, there is provided an abnormality compensation apparatus.
The abnormality compensation device of the present invention includes: the system comprises a submission module, a database and a processing module, wherein the submission module is used for receiving an abnormal compensation task submitted by at least one application server and storing the abnormal compensation task to the database; and the execution module is used for respectively starting corresponding execution threads for the abnormal compensation tasks under each application server, grabbing the abnormal compensation tasks from the database based on the execution threads, and executing the abnormal compensation tasks in an RPC (remote procedure call) mode under the condition that the abnormal compensation tasks meet preset execution conditions.
Optionally, the execution module is further configured to, when the exception compensation task does not meet a preset execution condition, grab a next exception compensation task from the database.
Optionally, the preset execution condition configured by the execution module includes: the task state of the abnormal compensation task is a creation state, and/or the current time meets an execution time strategy of the abnormal compensation task; wherein the creation status indicates that the exception compensation task has not been successfully executed and that the number of execution failures is less than or equal to a suspend threshold.
Optionally, the execution module is further configured to update the number of execution failures of the exception compensation task when the execution of the exception compensation task fails; and updating the task state of the exception compensation task to a suspended state when the updated execution failure times are greater than a task suspended threshold; the execution module is further configured to update the task state of the abnormal compensation task to a successful state when the abnormal compensation task is successfully executed.
Optionally, the submission module is further configured to, before the operation of saving the abnormal compensation task to the database is performed, confirm that the database has application access information that matches the application server identifier carried in the abnormal compensation task, and/or confirm that the abnormal compensation task is not repeatedly submitted; wherein the application access information comprises: and identification of the accessed application server.
Optionally, the apparatus further comprises: the monitoring module is used for monitoring the execution condition of the abnormal compensation task in the database; the system is also used for triggering alarm operation under the condition that the total number of the abnormal compensation tasks under the same application server side or the total number of the abnormal compensation tasks under the same task type exceeds a first threshold value; and/or triggering alarm operation under the condition that the total number of the abnormal compensation tasks in the suspended state under the same application server side or the total number of the abnormal compensation tasks in the suspended state under the same task type exceeds a second threshold value.
Optionally, the apparatus further comprises: and the configuration module is used for configuring the application access information and storing the application access information to the database.
To achieve the above object, according to still another aspect of the present invention, there is provided an electronic apparatus.
The electronic device of the present invention includes: one or more processors; and storage means 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 anomaly compensation method of the present invention.
To achieve the above object, according to still another aspect of the present invention, there is provided a computer-readable medium.
The computer-readable medium of the present invention has stored thereon a computer program which, when executed by a processor, implements the anomaly compensation method of the present invention.
One embodiment of the above invention has the following advantages or benefits: the anomaly compensation method comprises the steps that anomaly compensation tasks submitted by at least one application server are stored in a database, the anomaly compensation tasks are executed in an RPC calling mode, and therefore the anomaly compensation can be uniformly compensated for the anomalies of each application server, decoupling of anomaly compensation logic and application server business logic is achieved, development cost is reduced, and maintainability of the anomaly compensation logic is improved; by starting a corresponding execution thread for each application server, capturing an abnormal compensation task from the database based on the execution thread, executing the abnormal compensation task under the condition of meeting a preset execution condition and the like, the mutual influence of the abnormal compensation tasks of different application servers in the execution process can be prevented, and the execution logic of the abnormal compensation task is optimized.
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 an anomaly compensation method according to a first embodiment of the present invention;
FIG. 2 is a schematic diagram of the main steps of an anomaly compensation method according to a second embodiment of the present invention;
FIG. 3 is a schematic diagram of an exception compensation task submission flow according to a third embodiment of the present invention;
FIG. 4 is a schematic view of an anomaly compensation task monitoring flow according to a fourth embodiment of the present invention;
fig. 5 is a main block schematic diagram of an abnormality compensation apparatus according to a fifth embodiment of the present invention;
fig. 6 is a main block schematic diagram of an abnormality compensation apparatus according to a sixth embodiment of the present invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
FIG. 8 is a schematic block diagram of a computer system suitable for use with the electronic device to implement an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present 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.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.
Before describing embodiments of the present invention in detail, some technical terms related to the embodiments of the present invention will be described.
MQ: a Message Queue (Message Queue) is a communication method between processes or between different threads of the same process.
RPC: remote Procedure Call (Remote Procedure Call), is a computer communication protocol.
Mysql: is a relational database.
First embodiment
Fig. 1 is a schematic diagram of main steps of an abnormality compensation method according to a first embodiment of the present invention. As shown in fig. 1, the anomaly compensation method according to the embodiment of the present invention includes:
step S101, receiving an abnormal compensation task submitted by at least one application server, and storing the abnormal compensation task to a database.
Illustratively, the application server (also referred to as application system or service system) may be an order system, an inventory system, or the like. The anomaly compensation task submitted by the application server can comprise information such as an application server identifier (or called an application identifier, which can be represented by Appid), a task type, interface access parameters required by RPC calling and the like. In particular implementation, when an abnormality occurs at the application server (for example, the application server fails to send a message to the MQ), an abnormality compensation task may be submitted to the abnormality compensation device in the present invention.
And S102, respectively starting corresponding execution threads for the abnormal compensation tasks under each application server, and capturing the abnormal compensation tasks from the database based on the execution threads.
For example, if 5 application server exception compensation tasks are stored in the database, 5 execution threads may be set, and each execution thread is responsible for executing one application server exception compensation task.
And step S103, executing the abnormal compensation task in an RPC calling mode under the condition that the abnormal compensation task meets preset execution conditions.
In an optional embodiment, the preset execution condition includes: the task state of the exception compensation task is a creation state (also referred to as an "incomplete state"). Wherein the creation status indicates that the exception compensation task has not been successfully executed and that the number of execution failures is less than or equal to a task suspension threshold.
In another optional embodiment, the preset execution condition includes: and the task state of the abnormal compensation task is a creation state, and the current time meets the execution time strategy of the abnormal compensation task. Wherein the execution time policy may include: a predetermined execution time interval, a predetermined execution time. In specific implementation, if the predetermined execution time is earlier than or equal to the current time, the current time may be considered to satisfy the execution time policy of the task for compensating the anomaly.
And step S104, when the abnormality compensation task does not meet the execution condition, grabbing the next abnormality compensation task from the database based on the execution thread.
In the embodiment of the invention, the abnormity compensation task submitted by at least one application server is stored in the database, and is executed in an RPC calling mode, so that the abnormity of each application server can be uniformly compensated, the decoupling of the abnormity compensation logic and the service logic of the application server is realized, the development cost is reduced, and the maintainability of the abnormity compensation logic is improved; by starting a corresponding execution thread for each application server, capturing an abnormal compensation task from the database based on the execution thread, executing the abnormal compensation task under the condition of meeting a preset execution condition and the like, the abnormal compensation tasks of different application servers can be prevented from influencing each other in the execution process, and the execution logic of the abnormal compensation task is optimized.
Second embodiment
Fig. 2 is a schematic diagram of the main steps of an anomaly compensation method according to a second embodiment of the present invention. As shown in fig. 2, the anomaly compensation method according to the embodiment of the present invention includes:
step S201, receiving an abnormal compensation task submitted by at least one application server, and storing the abnormal compensation task to a database.
The exception compensation task submitted by the application server side can comprise information such as an application identifier (Appid), a task type and interface access parameters required by RPC calling. In particular implementation, when an exception occurs (for example, the application server fails to send a message to the MQ), the application server may submit an exception compensation task to the exception compensation device in the present invention.
Step S202, corresponding execution threads are respectively started for the abnormal compensation tasks under each application server, and the abnormal compensation tasks are captured from the database based on the execution threads.
For example, if 5 application server exception compensation tasks are stored in the database, 5 execution threads may be set, and each execution thread is responsible for executing one application server exception compensation task.
And step S203, judging whether the abnormal compensation task meets the preset execution condition. Executing step S204 when the abnormality compensation task satisfies a preset execution condition; in the case where the abnormality compensation task does not satisfy the preset execution condition, step S205 is executed.
In an optional embodiment, the preset execution condition includes: the task state of the abnormality compensation task is a creation state (also referred to as an "incomplete state"), and the current time satisfies an execution time policy of the abnormality compensation task. Wherein the creation status indicates that the exception compensation task has not been successfully executed and that the number of execution failures is less than or equal to a task suspension threshold. Wherein the execution time policy may include: a predetermined execution time interval, a predetermined execution time. In specific implementation, if the predetermined execution time is earlier than or equal to the current time, the current time may be considered to satisfy the execution time policy of the task for compensating the anomaly.
In the embodiment of the present invention, in addition to the creation state, the task state of the task for compensating for the anomaly in the database may further include: a success state and a suspend state. The success status indicates that the execution of the exception compensation task was successful, and the suspend status indicates that the execution of the exception compensation task was suspended. In this step, if the exception compensation task captured by the execution thread is in the suspend state or the success state, step S205 may be executed, that is, the processing flow of the exception compensation task is ended; if the state of the abnormal compensation task captured by the execution thread is the creation state, whether the current time meets the execution time strategy of the abnormal compensation task can be further judged. If the current time meets the execution time policy of the abnormal compensation task, step S204 may be executed; otherwise, step S205 may be executed, that is, the processing flow of the task of compensating the anomaly is ended.
And step S204, executing the abnormity compensation task in an RPC calling mode. After step S204, step S206 is executed.
In the step, an RPC call request can be assembled according to information such as interface entry parameters required by RPC calls in the exception compensation task, and the RPC call request is sent to the application server to execute the exception compensation task. For example, the application server a may submit the anomaly compensation task 1 to the anomaly compensation device in the present invention after failing to send the message to the MQ. Under the condition that the anomaly compensation task 1 meets the preset execution condition, the anomaly compensation device can assemble an RPC call request and send the RPC call request to the application server A so as to retry the service logic of sending the message to the MQ.
And step S205 is ended.
In this step, the ending may be understood as ending the processing flow of this exceptional compensation task for grabbing. And then, capturing the next abnormity compensation task under the same application server from the database through the execution thread.
And step S206, judging whether the execution of the abnormal compensation task is successful. If the execution of the abnormality compensation task is successful, executing step S207; in the case where the execution of the abnormality compensation task fails, step S208 is executed.
In this step, whether the exception compensation task is successfully executed may be determined according to response information of the RPC call request. For example, when response information of successful execution returned by the application server is received, the execution of the anomaly compensation task can be considered to be successful; and under the condition that response information of execution failure returned by the application server is received, the abnormal compensation task can be considered to be failed to execute.
And step S207, updating the task state of the abnormality compensation task to a success state.
In this step, the task state of the exception compensation task in the database may be updated from the creation state to the success state.
And step S208, updating the execution failure times of the abnormality compensation task. After step S208, step S209 may be performed.
In this step, an operation of adding 1 may be performed on the number of execution failures of the abnormality compensation task in the database. For example, the number of execution failures of the abnormality compensation task before updating is 10, and the number of execution failures after updating is 11.
Step S209, determining whether the execution failure number of the abnormality compensation task is greater than a task suspension threshold. Step S210 may be performed if the number of execution failures of the abnormality compensation task is greater than a task suspension threshold; in a case where the number of execution failures of the abnormality compensation task is less than or equal to the task suspension threshold, step S205 may be executed.
Wherein, the task suspension threshold value can be set according to actual requirements. For example, the task suspension threshold may be set to 15 times, 20 times, or other values. In specific implementation, if the execution time policy is configured for the exception compensation task, after it is determined that the number of execution failures is less than the task suspension threshold, the following steps may be further performed: and modifying the preset execution time of the next execution of the abnormal compensation task according to the preset execution interval in the execution time strategy.
And step S210, updating the task state of the abnormity compensation task to be a suspended state.
In this step, the task state of the task in the database for compensating for the anomaly may be updated from the creation state to the suspension state.
Further, before step S201, the method of the embodiment of the present invention may further include the following steps: configuring information such as application access information, a task type corresponding to an accessed application server (or called as access application), an RPC interface, an execution time policy and the like, and storing the configured information to a database. Wherein the application access information may include: identification of an accessed application server (also called as an "access application"), and service description information of the access application. In particular, an access application may correspond to one or more task types.
In the embodiment of the invention, the abnormal condition of each application server can be uniformly compensated through the steps. Compared with the prior art, the anomaly compensation method provided by the embodiment of the invention at least has the following advantages: 1. the decoupling of the abnormal compensation logic and the application server business logic is realized, the development cost is reduced, and the maintainability of the abnormal compensation logic is improved; 2. the execution thread is started according to the application dimension, and the abnormal compensation tasks are captured from the database based on the execution thread, so that the abnormal compensation tasks of different application servers can be prevented from being influenced with each other in the execution process, and the processing logic of abnormal compensation is optimized; 3. by setting the execution condition based on factors such as task state and the like and executing the abnormal compensation task when the execution condition is met, the problems of overhigh load of an application server, reduced concurrency capability of a system and the like caused by retry of the abnormal compensation task all the time can be avoided.
Third embodiment
The embodiment of the invention provides an anomaly compensation method, which further optimizes the submission flow of an anomaly compensation task. Fig. 3 is a schematic diagram illustrating a submission flow of an anomaly compensation task according to an embodiment of the present invention. As shown in fig. 3, the submission flow of the anomaly compensation task in the embodiment of the present invention includes:
and S301, receiving an abnormal compensation task submitted by an application server.
Wherein the anomaly compensation task may include the following information: and the application server identification (Appid), the task type and the interface access parameter required by RPC calling. In particular implementation, after an exception occurs (for example, the application server fails to send a message to the MQ), the application server may submit an exception compensation task to the exception compensation device in the present invention.
Step S302, judging whether application access information matched with the application identification carried by the abnormal compensation task exists in a database. If the matched application access information exists in the database, executing step S303; in case the matching application access information does not exist in the database, step S304 is performed.
In the embodiment of the present invention, the database may store the application access information of one or more application servers configured in advance. The application access information may include: the identification of the accessed application server (also called "application identification") and the service description information of the application server. In specific implementation, a database can be queried according to the application server identifier carried by the received abnormal compensation task, and if application access information matched with the application server identifier exists, step S303 is executed; otherwise, step S304 is performed.
And step S303, judging whether the abnormal compensation task is repeatedly submitted. In a case where the abnormality compensation task is not repeatedly submitted, executing step S305; in the case where the abnormality compensation task is repeatedly submitted, step S304 is performed.
In an alternative embodiment, a unique task identifier (uuid) may be generated from the received exception compensation task and the database may be queried based on the unique task identifier. If the database has the abnormal compensation task with the unique task identifier, the received abnormal compensation task is considered to be repeatedly submitted; and if the database does not have the abnormal compensation task with the unique task identifier, the received abnormal compensation task is not considered to be repeatedly submitted.
And step S304, returning response information of failed submission to the application server.
And S305, storing the abnormal compensation task submitted by the application server to a database. After step S305, step S306 may be performed.
The exception compensation task can comprise information such as an application identifier, a task type, an RPC call interface, an interface entry parameter required by the RPC call and the like. In particular implementations, the information included in the anomaly compensation tasks may be stored in one or more database tables.
And step S306, returning response information of successful submission to the application server.
In the embodiment of the invention, the submission request of the application server which is not accessed can be rejected by verifying the application server which submits the abnormal compensation task; by checking whether the received abnormal compensation task is repeatedly submitted or not, the problem of repeated submission of the abnormal compensation task can be avoided. By executing the exception compensation task submission process of the embodiment of the invention, the exception compensation processing logic of the invention can be further optimized.
Fourth embodiment
The embodiment of the invention provides an anomaly compensation method. The abnormality compensation method includes a monitoring process of the abnormality compensation task in addition to the process shown in fig. 2. Fig. 4 is a schematic view of a monitoring flow of an anomaly compensation task according to an embodiment of the present invention. As shown in fig. 4, the monitoring process of the anomaly compensation task in the embodiment of the present invention includes:
and S401, monitoring the execution condition of the abnormal compensation task in the database.
In the embodiment of the invention, the monitoring thread can be started according to the dimension of the application server, and the abnormal compensation task under the same application server is monitored based on the monitoring thread.
In another embodiment, a monitoring thread may also be started according to a task type dimension, and an exception compensation task of the same task type is monitored based on the monitoring thread.
Step S402, judging whether the total number of the abnormal compensation tasks under the same application server exceeds a first threshold value. Executing step S404 under the condition that the total number of the abnormal compensation tasks under the same application server exceeds a first threshold value; otherwise, step S403 is performed.
Step S403, determining whether the number of tasks in the suspended state under the same application server exceeds a second threshold. If yes, go to step S404; if not, step S405 can be executed.
In specific implementation, the first threshold and the second threshold can be set according to actual requirements.
And step S404, triggering alarm operation.
Illustratively, the alert operation may include: and sending an alarm notice to a pre-configured alarm contact. For example, an alert notification may be sent by mail to an alert contact.
And step S405, ending.
In the embodiment of the invention, the execution condition of the abnormal compensation task can be monitored and alarmed through the steps, and the abnormal compensation processing logic in the invention is further optimized.
Fifth embodiment
Fig. 5 is a schematic view of main blocks of an abnormality compensation apparatus according to a fifth embodiment of the present invention. As shown in fig. 5, an abnormality compensation apparatus 500 of an embodiment of the present invention includes: a submission module 501 and an execution module 502.
The submission module 501 is configured to receive an exception compensation task submitted by at least one application server, and store the exception compensation task in a database.
The exception compensation task submitted by the application server side can comprise: and the application server side identifier (or called as an application identifier and can be represented by Appid), the task type, the interface access parameter required by RPC calling and the like. In particular embodiments, when an exception occurs (e.g., the application server fails to send a message to the MQ), the application server may submit an exception compensation task to the submission module 501.
The execution module 502 is configured to respectively start a corresponding execution thread for the exception compensation task under each application server, and capture the exception compensation task from the database based on the execution thread.
For example, if 5 application server exception compensation tasks are stored in the database, 5 execution threads may be set, and each execution thread is responsible for executing an exception compensation task under one application server.
The execution module 502 is further configured to execute the exception compensation task in an RPC call manner when the exception compensation task meets a preset execution condition.
In an alternative embodiment, the execution conditions adopted by the execution module 502 include: the task state of the exception compensation task is a creation state (also referred to as an "incomplete state"). Wherein the creation state indicates that the exception compensation task has not been successfully executed and that the number of execution failures is less than or equal to a task suspension threshold.
In another alternative embodiment, the execution conditions employed by the execution module 502 include: the task state of the abnormality compensation task is a creation state (also referred to as an "incomplete state"), and the current time satisfies an execution time policy of the abnormality compensation task. Wherein the execution time policy may include: a predetermined execution time interval, a predetermined execution time. In specific implementation, if the predetermined execution time is earlier than or equal to the current time, the current time may be considered to satisfy the execution time policy of the task for compensating the anomaly.
The execution module 502 may be further configured to, when the exception compensation task does not meet a preset execution condition, fetch a next exception compensation task from the database based on the execution thread. In the anomaly compensation device of the embodiment of the invention, the anomaly compensation task submitted by at least one application server is stored in the database through the submission module 501, and the anomaly compensation task is executed in an RPC calling mode through the execution module 502, so that the anomaly of each application server can be uniformly compensated, the decoupling of the anomaly compensation logic and the service logic of the application server is realized, the development cost is reduced, and the maintainability of the anomaly compensation logic is improved; by starting the execution thread according to the application server dimension, capturing the abnormal compensation task from the database based on the execution thread, executing the abnormal compensation task when the preset execution condition is met, and the like, the abnormal compensation tasks of different application servers can be prevented from influencing each other in the execution process, and the processing logic of abnormal compensation is optimized.
Sixth embodiment
Fig. 6 is a schematic block diagram of an abnormality compensation apparatus according to an embodiment of the present invention. As shown in fig. 6, an abnormality compensation apparatus 600 of an embodiment of the present invention includes: a configuration module 601, a submission module 602, an execution module 603, and a monitoring module 604.
The configuration module 601 is configured to configure application access information and store the application access information in a database. Wherein the application access information may include: identification of an accessed application server (also called as an "access application"), and service description information of the access application. In addition, the configuration module 601 may be further configured to configure information such as a task type, an RPC interface, and an execution time policy corresponding to the access application. In particular, an access application may correspond to one or more task types.
The submission module 602 is configured to receive an exception compensation task submitted by at least one application server, and store the exception compensation task in a database. The exception compensation task submitted by the application server side can comprise: and the application server side identifier (or called as an application identifier and can be represented by Appid), the task type, the interface access parameter required by RPC calling and the like.
The submitting module 602 may further be configured to, before performing an operation of saving the abnormal compensation task to the database, confirm that the database has application access information that matches the application server identifier carried by the received abnormal compensation task, and/or confirm that the received abnormal compensation task is not repeatedly submitted. The application access information may include an identifier of an accessed application server.
Further, the submission module 602 may be further configured to return response information of successful submission to the application server after the exception compensation task is saved in the database. And after confirming that there is no matched application access information in the database or confirming that the exception compensation task is repeatedly submitted, the submission module 602 may be further configured to return response information indicating that the submission fails to the application server.
The executing module 603 is configured to respectively start a corresponding execution thread for the exception compensation task at each application server, and capture the exception compensation task from the database based on the execution thread. The execution module 603 is further configured to execute the exception compensation task in an RPC call manner when the exception compensation task meets a preset execution condition; the executing module 603 is further configured to, when the exception compensation task does not meet the preset executing condition, fetch a next exception compensation task from the database.
The execution conditions adopted by the execution module 603 may include: and the task state of the abnormal compensation task is a creation state, and/or the current time meets the execution time strategy of the abnormal compensation task. Wherein the creation state indicates that the exception compensation task has not been successfully executed and that the number of execution failures is less than or equal to a suspend threshold.
In the embodiment of the present invention, the task of compensating for the anomaly in the database may further include: success state, suspend state. The success status indicates that the execution of the exception compensation task was successful, and the suspend status indicates that the execution of the exception compensation task was suspended. During specific implementation, if the captured abnormal compensation task is in a suspended state or a successful state, the execution thread finishes the processing flow of the abnormal compensation task; if the captured abnormal compensation task is in a creation state, the execution thread can further judge whether the current time meets the execution time strategy of the abnormal compensation task. If the execution time strategy of the abnormal compensation task is met, the execution thread executes the abnormal compensation task in an RPC calling mode; if not, the execution thread can end the processing flow of the exception compensation task.
Further, the execution module 603 may be further configured to update the number of execution failures of the exception compensation task when the execution of the exception compensation task fails; and the task state of the abnormality compensation task is updated to the suspended state under the condition that the updated execution failure times are greater than the task suspended threshold value. The executing module 603 may be further configured to update the task state of the exception compensation task to a successful state when the exception compensation task is successfully executed.
And a monitoring module 604, configured to monitor an execution condition of the abnormal compensation task in the database. The monitoring module 604 may also be configured to trigger an alarm operation when the total number of the abnormal compensation tasks at the same application server or the total number of the abnormal compensation tasks in the same task type exceeds a first threshold; and/or triggering alarm operation under the condition that the total number of the abnormal compensation tasks in the suspended state under the same application server side or the total number of the abnormal compensation tasks in the suspended state under the same task type exceeds a second threshold value. Wherein the alarm operation may include: and sending an alarm notice to a pre-configured alarm contact. For example, an alert notification is sent to an alert contact by mail.
In the embodiment of the invention, the abnormal compensation tasks of the application servers can be uniformly compensated through the device. Compared with the prior art, the abnormity compensation device provided by the embodiment of the invention at least has the following advantages: 1. the decoupling of the abnormal compensation logic and the application server business logic is realized, the development cost is reduced, and the maintainability of the abnormal compensation logic is improved; 2. the execution thread is started according to the dimensionality of the application server, and the abnormal compensation tasks are captured from the database based on the execution thread, so that the abnormal compensation tasks of different application servers can be prevented from influencing each other in the execution process, and the processing logic of abnormal compensation is optimized; 3. by setting an execution condition based on factors such as task state and the like and executing the abnormal compensation task when the execution condition is met, the problems of overhigh load of an application server, reduced concurrency capability of a system and the like caused by always retrying the abnormal compensation task can be avoided; 4. the application server can access the abnormal compensation device only by simple configuration, so that the access cost is reduced; 5. and the execution condition of the abnormal compensation task is monitored and alarmed, so that the processing logic of the abnormal compensation is optimized.
Fig. 7 shows an exemplary system architecture to which the abnormality compensation method or abnormality compensation apparatus of the embodiment of the present invention can be applied.
As shown in fig. 7, the system architecture may include: an anomaly compensation device 701, an application server a 702, an application server B703 and an application server C703.
After the application server a 702, the application server B703 and the application server C703 are abnormal, a request for submitting an abnormality compensation task may be sent to the abnormality compensation device 701. The application server a 702, the application server B703 and the application server C703 may also receive an RPC call request from the anomaly compensation apparatus 701. For example, the application server A701 may submit the exception compensation task 1 to the exception compensation device 701 upon failure to send a message to the MQ. The exception compensation device 701 may assemble an RPC call request and send the RPC call request to the application server a to retry the service logic sending the message to the MQ, if the exception compensation task 1 meets the execution condition.
The anomaly compensation device 701 can be used for storing anomaly compensation tasks submitted by the application server A702, the application server B703 and the application server C703 to a database; starting an execution thread according to the application dimension, and capturing an abnormal compensation task from the database based on the execution thread; and executing the exception compensation processing logic such as the exception compensation task in an RPC calling mode under the condition that the exception compensation task meets the execution condition.
It should be understood that the number of application servers in fig. 7 is merely illustrative. There may be any number of application servers, as desired for implementation.
FIG. 8 illustrates a schematic block diagram of a computer system 800 suitable for use in implementing an electronic device of an embodiment of the invention. The system shown in fig. 8 is only an example, and should not bring any limitation to the function and the scope of use of the embodiments of the present invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 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 can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program executes the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 801.
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 includes a commit module and an execute module. The names of the modules do not limit the modules themselves under certain conditions, for example, the submission module can also be described as a module for receiving an exception compensation task submitted by at least one application server and saving the exception compensation task to a database.
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 perform the following: receiving an abnormal compensation task submitted by at least one application server, and storing the abnormal compensation task to a database; respectively starting corresponding execution threads for the abnormal compensation tasks under each application server, capturing the abnormal compensation tasks from the database based on the execution threads, and executing the abnormal compensation tasks in an RPC calling mode under the condition that the abnormal compensation tasks meet preset execution conditions.
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 (16)
1. An anomaly compensation method, characterized in that it comprises:
receiving an abnormal compensation task submitted by at least one application server, and storing the abnormal compensation task to a database;
respectively starting corresponding execution threads for the abnormal compensation tasks under each application server, capturing the abnormal compensation tasks from the database based on the execution threads, and executing the abnormal compensation tasks in an RPC calling mode under the condition that the abnormal compensation tasks meet preset execution conditions.
2. The method of claim 1, further comprising:
and under the condition that the abnormal compensation task does not meet the preset execution condition, capturing the next abnormal compensation task from the database based on the execution thread.
3. The method according to claim 1, wherein the preset execution condition comprises: the task state of the abnormal compensation task is a creation state, and/or the current time meets an execution time strategy of the abnormal compensation task; wherein the creation status indicates that the exception compensation task has not been successfully executed and that the number of execution failures is less than or equal to a task suspension threshold.
4. The method of claim 3, further comprising: after the step of executing the abnormal compensation task in an RPC calling mode, if the abnormal compensation task fails to be executed, updating the execution failure times of the abnormal compensation task; and updating the task state of the exception compensation task to a suspended state when the updated execution failure times are greater than a task suspended threshold; and under the condition that the execution of the abnormity compensation task is successful, updating the task state of the abnormity compensation task to be a success state.
5. The method of claim 1, further comprising:
before the step of storing the abnormal compensation task into a database is executed, confirming that the database has application access information matched with an application server identifier carried by the abnormal compensation task, and/or confirming that the abnormal compensation task is not repeatedly submitted; wherein the application access information comprises: and identification of the accessed application server.
6. The method of claim 1, further comprising:
monitoring the execution condition of the abnormal compensation task in the database; triggering alarm operation under the condition that the total number of the abnormal compensation tasks under the same application server side or the total number of the abnormal compensation tasks under the same task type exceeds a first threshold value; and/or triggering alarm operation under the condition that the total number of the abnormal compensation tasks in the suspended state under the same application server side or the total number of the abnormal compensation tasks in the suspended state under the same task type exceeds a second threshold value.
7. The method of claim 5, further comprising:
and configuring the application access information and storing the application access information to the database.
8. An anomaly compensation apparatus, said apparatus comprising:
the system comprises a submission module, a database and a processing module, wherein the submission module is used for receiving an abnormal compensation task submitted by at least one application server and storing the abnormal compensation task to the database;
and the execution module is used for respectively starting corresponding execution threads for the abnormal compensation tasks under each application server, grabbing the abnormal compensation tasks from the database based on the execution threads, and executing the abnormal compensation tasks in an RPC (remote procedure call) mode under the condition that the abnormal compensation tasks meet preset execution conditions.
9. The apparatus of claim 8, wherein the execution module is further configured to fetch a next task from the database if the task does not satisfy a preset execution condition.
10. The apparatus of claim 8, wherein the preset execution condition configured by the execution module comprises: the task state of the abnormal compensation task is a creation state, and/or the current time meets an execution time strategy of the abnormal compensation task; wherein the creation status indicates that the exception compensation task has not been successfully executed and that the number of execution failures is less than or equal to a suspend threshold.
11. The apparatus according to claim 10, wherein the execution module is further configured to update the number of execution failures of the task in case of the failure of the task; and updating the task state of the exception compensation task to a suspended state when the updated execution failure times are greater than a task suspended threshold; the execution module is further configured to update the task state of the abnormal compensation task to a successful state when the abnormal compensation task is successfully executed.
12. The apparatus according to claim 8, wherein the submission module is further configured to, before performing the operation of saving the exception compensation task to the database, confirm that the database has application access information matching an application server identifier carried in the exception compensation task, and/or confirm that the exception compensation task is not repeatedly submitted; wherein the application access information comprises: and identification of the accessed application server.
13. The apparatus of claim 8, further comprising:
the monitoring module is used for monitoring the execution condition of the abnormal compensation task in the database; the system is also used for triggering alarm operation under the condition that the total number of the abnormal compensation tasks under the same application server side or the total number of the abnormal compensation tasks under the same task type exceeds a first threshold value; and/or triggering alarm operation under the condition that the total number of the abnormal compensation tasks in the suspended state under the same application server side or the total number of the abnormal compensation tasks in the suspended state under the same task type exceeds a second threshold value.
14. The apparatus of claim 12, further comprising:
and the configuration module is used for configuring the application access information and storing the application access information to the database.
15. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
16. A computer-readable medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811465386.8A CN111258790B (en) | 2018-12-03 | 2018-12-03 | Anomaly compensation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811465386.8A CN111258790B (en) | 2018-12-03 | 2018-12-03 | Anomaly compensation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111258790A true CN111258790A (en) | 2020-06-09 |
| CN111258790B CN111258790B (en) | 2023-11-03 |
Family
ID=70946929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811465386.8A Active CN111258790B (en) | 2018-12-03 | 2018-12-03 | Anomaly compensation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258790B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111752740A (en) * | 2020-06-29 | 2020-10-09 | 深圳前海微众银行股份有限公司 | Microservice anomaly compensation method, microservice anomaly compensation device, microservice anomaly compensation equipment and computer readable storage medium |
| CN111813791A (en) * | 2020-06-17 | 2020-10-23 | 上海悦易网络信息技术有限公司 | Method and equipment for distributed transaction compensation |
| CN114024999A (en) * | 2022-01-10 | 2022-02-08 | 中航信移动科技有限公司 | Task compensation method, system, device, electronic equipment and storage medium |
| CN116560896A (en) * | 2023-07-11 | 2023-08-08 | 智慧眼科技股份有限公司 | Abnormality compensation method, device, equipment and storage medium |
| CN116909760A (en) * | 2023-09-13 | 2023-10-20 | 中移(苏州)软件技术有限公司 | Data processing method, device, readable storage medium and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6918053B1 (en) * | 2000-04-28 | 2005-07-12 | Microsoft Corporation | Compensation framework for long running transactions |
| US20160048790A1 (en) * | 2014-08-13 | 2016-02-18 | Daniel Ritter | Classification and modelling of exception types for integration middleware systems |
| CN108093005A (en) * | 2016-11-22 | 2018-05-29 | 北京京东尚科信息技术有限公司 | A kind of management method and system of interface exception call |
| CN108880873A (en) * | 2018-06-05 | 2018-11-23 | 中国农业银行股份有限公司 | A kind of affairs compensation method and device applied to heterogeneous system |
-
2018
- 2018-12-03 CN CN201811465386.8A patent/CN111258790B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6918053B1 (en) * | 2000-04-28 | 2005-07-12 | Microsoft Corporation | Compensation framework for long running transactions |
| US20160048790A1 (en) * | 2014-08-13 | 2016-02-18 | Daniel Ritter | Classification and modelling of exception types for integration middleware systems |
| CN108093005A (en) * | 2016-11-22 | 2018-05-29 | 北京京东尚科信息技术有限公司 | A kind of management method and system of interface exception call |
| CN108880873A (en) * | 2018-06-05 | 2018-11-23 | 中国农业银行股份有限公司 | A kind of affairs compensation method and device applied to heterogeneous system |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111813791A (en) * | 2020-06-17 | 2020-10-23 | 上海悦易网络信息技术有限公司 | Method and equipment for distributed transaction compensation |
| CN111813791B (en) * | 2020-06-17 | 2024-05-21 | 上海万物新生环保科技集团有限公司 | Distributed transaction compensation method and equipment |
| CN111752740A (en) * | 2020-06-29 | 2020-10-09 | 深圳前海微众银行股份有限公司 | Microservice anomaly compensation method, microservice anomaly compensation device, microservice anomaly compensation equipment and computer readable storage medium |
| CN114024999A (en) * | 2022-01-10 | 2022-02-08 | 中航信移动科技有限公司 | Task compensation method, system, device, electronic equipment and storage medium |
| CN116560896A (en) * | 2023-07-11 | 2023-08-08 | 智慧眼科技股份有限公司 | Abnormality compensation method, device, equipment and storage medium |
| CN116560896B (en) * | 2023-07-11 | 2023-10-10 | 智慧眼科技股份有限公司 | Abnormality compensation method, device, equipment and storage medium |
| CN116909760A (en) * | 2023-09-13 | 2023-10-20 | 中移(苏州)软件技术有限公司 | Data processing method, device, readable storage medium and electronic equipment |
| CN116909760B (en) * | 2023-09-13 | 2023-11-28 | 中移(苏州)软件技术有限公司 | Data processing method, device, readable storage medium and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111258790B (en) | 2023-11-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111258790B (en) | Anomaly compensation method and device | |
| CN108491301B (en) | Electronic device, abnormality early warning method based on redis and storage medium | |
| CN111427676B (en) | Robot flow automatic task processing method and device | |
| CN111176873A (en) | Micro-service automatic offline method and device, computer equipment and storage medium | |
| CN110611707B (en) | Task scheduling method and device | |
| CN112667382A (en) | Task scheduling method, device, equipment and storage medium | |
| CN108880873B (en) | Transaction compensation method and device applied to heterogeneous system | |
| CN112003947A (en) | System and verification method for preventing repeated requests from client to server | |
| CN115964153A (en) | Asynchronous task processing method, device, equipment and storage medium | |
| CN114090113B (en) | Method, device, equipment and storage medium for dynamically loading data source processing plug-in | |
| CN110941622A (en) | Data processing method and device | |
| CN113836155A (en) | Data processing method and device based on distributed system and storage medium | |
| CN114595074A (en) | Transaction failure rollback method and device in arrangement based on distributed scheduling | |
| CN112131188A (en) | Batch file distribution processing method and device | |
| CN116319758A (en) | Data migration method, device, electronic equipment and readable storage medium | |
| CN116226134A (en) | Method and device for writing data into file and data writing database | |
| CN114816866A (en) | Fault processing method and device, electronic equipment and storage medium | |
| CN111008202A (en) | Distributed transaction processing method and framework | |
| CN113742355A (en) | Method, device, equipment and computer readable medium for updating inventory | |
| CN111984484A (en) | Non-invasive micro-service access method and system | |
| CN111179097B (en) | Method, device, electronic equipment and storage medium for modifying warranty | |
| CN113269605B (en) | Order processing method, apparatus, device and computer readable medium | |
| US9158615B2 (en) | Method and apparatus for managing system | |
| CN113656424B (en) | Associated data processing method, system, equipment and medium for redundant storage of data table | |
| CN113176967B (en) | Data processing method and device, electronic equipment and computer readable storage medium |
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 |