Interrupt recovery method and device, electronic equipment, storage medium and product

Abstract

The invention discloses an interrupt recovery method and device, electronic equipment, a storage medium and a product, and relates to the technical field of computers. The method comprises the steps of obtaining operation parameters of a to-be-executed business task, and executing the business task based on the operation parameters; obtaining operation information of the business task, and determining whether the business task is interrupted based on the operation information; if the business task is interrupted, determining a target data storage specification based on a preset expansion coefficient and a data storage specification of the business task under the condition that the interruption type is data centralized interruption; and generating a recovery service task corresponding to the service task based on the attribute information of the service task and the target data storage specification, and executing the recovery service task. Through the technical scheme of the embodiment of the invention, the recovery efficiency and stability after the business task is interrupted can be effectively improved, the manual intervention cost is reduced, and the automatic operation and maintenance requirements of a large-scale system are better met.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an interrupt recovery method, apparatus, electronic device, storage medium and product. Background Technology

[0002] In modern information technology scenarios such as large-scale data processing, distributed computing, and cloud computing environments, the stable execution of business tasks (such as batch financial settlement and data aggregation) is crucial for ensuring system reliability and business continuity. However, in actual operation, task interruptions caused by dataset anomalies (such as insufficient preset data storage specifications) are becoming increasingly prominent and have become a major bottleneck restricting system availability.

[0003] Existing methods for recovering from task interruptions caused by dataset anomalies mostly rely on manual operation. This is not only inefficient, but also highly dependent on the experience of the staff, lacks stability, and incurs high labor costs, making it difficult to meet the maintenance needs of large-scale systems.

[0004] Therefore, there is an urgent need to propose a new method to solve the above problems. Summary of the Invention

[0005] This invention provides an interruption recovery method, apparatus, electronic device, storage medium, and product, which can effectively improve the recovery efficiency and stability after business task interruption, reduce the cost of manual intervention, and better meet the automated operation and maintenance needs of large-scale systems.

[0006] In a first aspect, embodiments of the present invention provide an interruption recovery method, the method comprising:

[0007] Obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters;

[0008] Obtain the operation information of the business task, and determine whether the business task has been interrupted based on the operation information;

[0009] If the business task is interrupted, and the interruption type is dataset interruption, the target data storage specification is determined based on the preset expansion coefficient and the data storage specification of the business task.

[0010] Based on the attribute information of the business task and the target data storage specifications, a recovery business task corresponding to the business task is generated and executed.

[0011] The technical solution of this invention first obtains the job parameters of the business task to be executed, and then executes the business task based on the job parameters, realizing the standardization and automation of the task, and providing a unified data benchmark and basis for subsequent monitoring, diagnosis and recovery. Next, it obtains the operation information of the business task, and determines whether the business task has been interrupted based on the operation information, realizing real-time monitoring and accurate fault detection of the business task, avoiding prolonged business stagnation due to failure to detect interruption faults in a timely manner. Then, if the business task is interrupted, in the case of a dataset interruption, the target data storage specification is determined based on a preset expansion coefficient and the data storage specification of the business task. This allows for rapid determination of the target data storage specification, shortening the recovery time caused by data storage problems and improving the efficiency of automated recovery; at the same time, it ensures the compatibility of the target data storage specification with the original business task configuration, reducing the risk of failure in restoring the business task. Finally, based on the attribute information of the business task and the target data storage specification, a recovery business task corresponding to the business task is generated and executed, realizing automated recovery after dataset interruption. This reduces the cost of manual intervention and the risk of configuration errors, improves the efficiency and reliability of interruption recovery, thereby ensuring business continuity and system stability, and effectively reducing the probability of secondary interruptions. Therefore, the technical solution of the present invention solves the problems of low interruption recovery efficiency, insufficient stability, high labor costs, and inability to adapt to the operation and maintenance needs of large-scale systems caused by reliance on manual operation in the prior art.

[0012] Secondly, embodiments of the present invention also provide an interruption recovery device, the device comprising:

[0013] The execution module is used to obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters;

[0014] The judgment module is used to obtain the operation information of the business task and determine whether the business task has been interrupted based on the operation information;

[0015] The determination module is used to determine the target data storage specification based on a preset expansion coefficient and the data storage specification of the business task if the business task is interrupted, and the interruption type is a dataset interruption.

[0016] The recovery module is used to generate a recovery business task corresponding to the business task based on the attribute information of the business task and the target data storage specifications, and to execute the recovery business task.

[0017] Thirdly, embodiments of the present invention also provide an electronic device, the electronic device comprising:

[0018] At least one processor; and a memory communicatively connected to said at least one processor; wherein,

[0019] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform any of the interrupt recovery methods described in the first aspect.

[0020] Fourthly, embodiments of the present invention also provide a storage medium containing computer-executable instructions, which, when executed by a computer processor, implement any of the interrupt recovery methods described in the first aspect.

[0021] Fifthly, this application provides a computer program product comprising a computer program that, when executed by a processor, implements any of the interrupt recovery methods described in the first aspect.

[0022] It should be noted that the aforementioned computer instructions may be stored, in whole or in part, on a computer-readable storage medium. This computer-readable storage medium may be packaged together with the processor of the interrupt recovery device, or it may be packaged separately from the processor of the interrupt recovery device; this application does not impose any limitations on this.

[0023] The descriptions of the second, third, fourth, and fifth aspects in this application can be referenced to the detailed description of the first aspect; and the beneficial effects of the descriptions of the second, third, fourth, and fifth aspects can be referenced to the analysis of the beneficial effects of the first aspect, which will not be repeated here.

[0024] In this application, the name of the aforementioned interruption recovery device does not limit the device or functional module itself. In actual implementation, these devices or functional modules may appear under other names. As long as the function of each device or functional module is similar to that of this application, it falls within the scope of the claims of this application and its equivalents.

[0025] These or other aspects of this application will become more readily apparent in the following description. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a flowchart illustrating an interruption recovery method provided in an embodiment of the present invention.

[0028] Figure 2 A flowchart illustrating another interruption recovery method provided in an embodiment of the present invention;

[0029] Figure 3 This is a schematic diagram of the structure of an interrupt recovery device provided in an embodiment of the present invention;

[0030] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0031] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0032] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0033] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0034] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0035] Before discussing the exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the operations (or steps) as sequential processes, many of these operations can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but may also have additional steps not included in the figures. The process can correspond to a method, function, procedure, subroutine, subroutine, etc. Moreover, without conflict, the embodiments and features in the embodiments of the present invention can be combined with each other.

[0036] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0037] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0038] Figure 1 This is a flowchart illustrating an interruption recovery method provided in an embodiment of the present invention. This embodiment is applicable to situations requiring automatic recovery of business tasks that experience dataset interruptions during execution. The method can be executed by an interruption recovery device, which can be implemented in software and / or hardware. For example, the device can be integrated into an electronic device. (Reference) Figure 1 The interrupt recovery method in this embodiment specifically includes the following steps:

[0039] Step 110: Obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters.

[0040] Specifically, a business task (also known as an application job) refers to an execution instance initiated on a computer host (such as a server, mainframe, cloud host, etc.). Its core purpose is to complete a specific and complete business objective or computational task. It is an independent execution unit that carries out specific business operations (such as a single data synchronization, scheduled report generation, order processing, etc.). Job parameters refer to the configuration information required to execute a business task, used to specify the execution rules and dependencies of the task (such as execution time, data source address, processing threshold, job name, dataset path, etc.).

[0041] In practical implementation, existing scheduling tools can be used to write the business task to be executed into the shell job as parameters, thereby obtaining the complete job parameters of the business task. Next, the shell job is used to perform legality verification on the obtained job parameters (such as checking whether the parameters are complete, whether the format is correct, and whether the data source address is reachable). After successful verification, the shell job, as a unified execution entry point, carries these parameters and starts and executes the business task through a preset calling method (such as process call, interface call, script trigger, or submission by an internal subsystem based on the job control language). Here, the shell job acts as the "scheduling carrier and parameter transmission intermediary" for the business task. As a lightweight execution shell, its core functions include: loading job parameters, verifying parameters, and calling and starting the target business task. It does not directly undertake specific business logic processing, but is only responsible for process scheduling and dependency management; essentially, it is a single process or a group of related processes.

[0042] In this embodiment, the above steps achieve the standardization and automation of tasks, and provide a unified data benchmark and basis for subsequent monitoring, diagnosis and recovery.

[0043] Step 120: Obtain the operation information of the business task, and determine whether the business task has been interrupted based on the operation information.

[0044] Specifically, operational information refers to real-time status data generated during the execution of business tasks, reflecting the task's progress and status (such as whether it is running normally, execution progress, error messages, etc.). For example, operational information may include task logs, system return codes, performance metrics, progress percentage, data input / output rates, and specialized data storage monitoring metrics (such as disk usage). Interruption refers to the state in which a business task unexpectedly stops during execution due to unforeseen circumstances (such as insufficient resources, data problems, etc.) and fails to complete its predetermined process.

[0045] In practice, the unique identifier of a business task (such as a task number) can be used to obtain the task's running status information from the scheduling system (such as a job execution system). This running status information includes the real-time return code of the current business task. Then, the obtained return code is compared with a preset interruption return code set (such as 07). If the return code matches any code in the preset interruption return code set, it is determined that the business task has been interrupted; if the return code does not match any code in the preset interruption return code set, it is determined that the business task has not been interrupted. The preset interruption status code set is pre-set according to actual conditions or requirements, used to clearly identify the return codes for business task interruptions, and can be flexibly adjusted to adapt to the interruption determination requirements of different business tasks.

[0046] If it is determined that the business task has not been interrupted, the latest running status information is obtained, and the interruption judgment logic mentioned above is repeated based on the information until it is determined that the business task has been interrupted, or the business task is confirmed to have been completed normally (such as all steps returning preset success codes, the scheduling system marking the task as "execution completed", etc.), so as to ensure the task execution closed loop, avoid missing interruption scenarios, and improve the reliability of the process.

[0047] In this embodiment, the above steps enable real-time monitoring and accurate fault detection of business tasks, which can avoid long-term business interruption due to failure to detect interruption faults in time.

[0048] Step 130: If a business task is interrupted, and the interruption type is dataset interruption, determine the target data storage specification based on the preset expansion coefficient and the data storage specification of the business task.

[0049] Specifically, interruption type refers to the classification and identification of the reasons for interruption during the execution of business tasks. This clarifies the essential cause of the interruption, enabling targeted recovery strategies. Interruption types include dataset interruption, resource interruption, and program logic interruption. A dataset interruption refers to a specific type of interruption whose root cause is directly related to insufficient data storage, access, or processing capabilities. The preset expansion factor refers to a fixed percentage value pre-set based on actual conditions or needs. This value is used to calculate the expanded specifications based on the original data storage specifications. For example, the preset expansion factor can be 1.2, 1.5, 2.0, etc. Data storage specifications refer to the data storage resource configuration required during the execution of business tasks, including parameters such as storage capacity, read / write performance, and storage type. The target data storage specification refers to the data storage specification determined after expansion using the preset expansion factor for dataset interruption scenarios, used to support the recovery of business task execution.

[0050] In practice, after determining that a business task has been interrupted, keywords (such as "dataset not found," "insufficient storage capacity," "data read / write failure," and fault descriptions associated with return codes) can be extracted from the task's running status information. Then, based on these keywords, a matching query is performed in the keyword-interrupt type mapping table to obtain the specific interruption type of the business task. Next, it is determined whether the interruption type is a dataset interruption. If the interruption type is a dataset interruption, the data storage capacity of the business task is extracted from its data storage specifications. Then, the product of a preset expansion coefficient and the data storage capacity is calculated to obtain the target storage capacity. Finally, the target storage capacity is integrated with other parameters in the data storage specifications (excluding the data storage capacity) to generate the target data storage specifications. The keyword-interrupt type mapping table is a pre-defined mapping table based on actual conditions or requirements; for example, the keywords "storage full" or "Dataset full" correspond to dataset interruption, and the keyword "CPU 100%" corresponds to resource interruption.

[0051] If the interruption type is not a dataset interruption, an automated retry mechanism is triggered: the business task is automatically retried according to the preset number of retries (e.g., 3 times) and retry interval (e.g., 5 seconds for the first time, and doubled for each subsequent time); if the retry still fails after reaching the preset number of retries, the current task is immediately terminated, and detailed alarm information including "unique task identifier, interruption type, error log fragment, and interruption time" is pushed to the developers. After the developers have investigated and fixed the problem, they can manually trigger the task to run again through the scheduling system.

[0052] In this embodiment, the above steps enable rapid determination of the target data storage specifications, shortening the recovery time from interruptions caused by data storage issues and improving automated recovery efficiency. Simultaneously, it ensures compatibility between the target data storage specifications and the original business task configuration, reducing the risk of business task recovery failure.

[0053] Step 140: Generate a recovery business task corresponding to the business task based on the attribute information of the business task and the target data storage specifications, and execute the recovery business task.

[0054] Specifically, attribute information refers to data associated with the configuration and operation of business tasks, such as data sources, processing logic, job parameters, and dependencies. Recovering a business task refers to generating a new task based on the attribute information of the original business task and the target data storage specifications. Its purpose is to restore interrupted business processes and ensure the task is eventually completed.

[0055] In practice, a recovery business task with attributes completely identical to the original business task but with the same data storage specification as the target data storage task can be generated based on the attribute information of the business task and the target data storage specification. Then, the recovery business task is executed based on the job parameters of the original business task, and the original business task is deleted to ensure a closed-loop business process and no resource redundancy.

[0056] In this embodiment, the above steps enable automated recovery of the dataset after interruption, which reduces the cost of manual intervention and the risk of configuration errors, improves the efficiency and reliability of interruption recovery, and thus ensures business continuity and system stability, while effectively reducing the probability of secondary interruption.

[0057] The interruption recovery method provided in this invention first obtains the job parameters of the business task to be executed, and then executes the business task based on the job parameters. This achieves task standardization and automated driving, and provides a unified data benchmark and basis for subsequent monitoring, diagnosis, and recovery. Next, it obtains the operational information of the business task and determines whether the business task has been interrupted based on the operational information. This achieves real-time monitoring and accurate fault detection of the business task, avoiding prolonged business stagnation due to failure to detect interruption faults in a timely manner. Then, if the business task is interrupted, in the case of a dataset interruption, the target data storage specification is determined based on a preset expansion coefficient and the data storage specification of the business task. This allows for rapid determination of the target data storage specification, shortening the recovery time for interruptions caused by data storage problems and improving automated recovery efficiency. Simultaneously, it ensures compatibility between the target data storage specification and the original business task configuration, reducing the risk of failure in restoring the business task. Finally, based on the attribute information of the business task and the target data storage specification, a recovery business task corresponding to the business task is generated and executed. This achieves automated recovery after a dataset interruption, reducing the cost of manual intervention and the risk of configuration errors, while improving the efficiency and reliability of interruption recovery, thereby ensuring business continuity and system stability, and effectively reducing the probability of secondary interruptions. Therefore, the technical solution of the present invention solves the problems of low interruption recovery efficiency, insufficient stability, high labor costs, and inability to adapt to the operation and maintenance needs of large-scale systems caused by reliance on manual operation in the prior art.

[0058] Figure 2 This is a flowchart illustrating another interrupt recovery method provided by an embodiment of the present invention. This embodiment is a specific implementation based on the above embodiment. In this embodiment, the method may further include:

[0059] Step 210: Obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters.

[0060] Step 211: Obtain the operation information of the business task.

[0061] Step 212: Determine whether the business task has been interrupted based on the operation information.

[0062] If an interruption occurs, proceed to step 213; if no interruption occurs, proceed to step 211.

[0063] In practice, the system can first determine whether the business task has been interrupted based on the runtime information. If an interruption occurs, it means that the business task has not progressed normally according to the preset process. At this time, the interruption cause can be further analyzed to determine whether the interruption type is a dataset interruption, so as to trigger the corresponding recovery strategy in a targeted manner. If no interruption occurs, it means that the business task is in a normal execution state. At this time, the runtime information of the business task can be obtained to monitor the progress of the task in real time and predict potential risks in a timely manner.

[0064] Furthermore, step 212 may specifically include: matching the return code in the operation information with the preset interrupt code to obtain the matching result; if the matching result is a match, then it is determined that the business task has been interrupted.

[0065] Specifically, a return code refers to a status identifier returned by the scheduling system (such as the job input subsystem), execution engine, or application during the execution of a business task, used to intuitively reflect the execution result status of the task. A preset interruption code refers to a set of return codes predefined and stored according to actual conditions or needs, used to clearly identify when a business task has been interrupted, such as 07, 08, and 12. The matching result refers to the result obtained by comparing the actual return code extracted from the business task's execution information with the preset interruption codes, including both "match" and "non-match" cases.

[0066] In the specific implementation, after obtaining the operation information of the business task, the return code can be extracted and matched with the preset interrupt code (which can be configured as a single code value or a set of multiple code values) to obtain the matching result. The specific judgment rules are as follows: (1) The preset interrupt code is a single code value: when the extracted return code is consistent with the preset interrupt code, the matching result is determined to be a match, and the business task is determined to be interrupted; if they are inconsistent, the matching result is determined to be a mismatch, and the business task is determined not to be interrupted. (2) The preset interrupt code is a set of at least two code values: when the extracted return code is consistent with any one of the interrupt codes in the set, the matching result is determined to be a match, and the business task is determined to be interrupted; if it is inconsistent with all the interrupt codes in the set, the matching result is determined to be a mismatch, and the business task is determined not to be interrupted.

[0067] In this embodiment, the above steps not only improve the accuracy of interruption determination but also reduce implementation costs.

[0068] Step 213: Determine whether the interrupt type is a dataset interrupt.

[0069] If the dataset is interrupted, proceed to step 214; otherwise, proceed to step 216.

[0070] In practice, after confirming that a business task has been interrupted, keywords (such as error descriptions, fault prompts, return code associations, etc.) can be extracted from the task's runtime status information. Then, a matching query is performed in the keyword-interrupt type correspondence table to obtain the specific interruption type of the business task. Next, it is determined whether the interruption type is a dataset interruption. If the interruption type is a dataset interruption, it indicates that the interruption cause is related to data storage. In this case, the target data storage specification can be determined based on the preset expansion coefficient and the data storage specification of the business task to provide suitable storage resources for subsequent business task recovery. If the interruption type is not a dataset interruption, it indicates that the interruption cause is unrelated to data storage. In this case, the full runtime information of the business task can be obtained, providing comprehensive data support for subsequent staff to formulate corresponding processing strategies.

[0071] Step 214: Determine the target data storage specifications based on the preset expansion coefficient and the data storage specifications of the business tasks.

[0072] Step 215: Generate a recovery business task corresponding to the business task based on the attribute information of the business task and the target data storage specifications, and execute the recovery business task.

[0073] Optionally, the attribute information includes recovery attribute information.

[0074] Further, step 215 may specifically include: if the recovery attribute information of the business task is migration, then generate an initial recovery task based on the target data storage specification; migrate the source data corresponding to the business task to the storage carrier associated with the initial recovery task to obtain the recovery business task; execute the recovery business task based on the job parameters and the historical operation status of the business task, and delete the business task.

[0075] Specifically, recovery attribute information refers to the configuration information preset in the business task according to the actual situation or needs, used to define the recovery method after interruption. It is a key attribute that determines the generation logic of the recovery task. For example, recovery attribute information includes migration, creation, and continuation. Source data refers to all business data that the business task has processed, is pending processing, or is associated with before the interruption, including raw data obtained from the data source, intermediate data generated before the interruption, and result data to be written to the target storage. It is the core business data foundation that the recovery task needs to inherit. The initial recovery task refers to a transitional task instance generated based on the attribute information of the business task (such as data processing logic, job parameters, dependencies, etc.) and the target data storage specifications. Storage carrier refers to the physical or logical storage resources (such as server hard drives, cloud storage containers, database tablespaces, etc.) that conform to the target data storage specifications and are associated with the initial recovery task. It is the target location for source data migration and also the carrier for data reading and writing during the execution of the recovery task. Historical operation status refers to the record of the business task's running status before the interruption. Historical operation status includes completed execution steps, interruption node locations, data processing progress, and historical resource usage.

[0076] In the specific implementation, after determining that the interruption type is a dataset interruption, if the recovery attribute information of the business task is migration, the data storage specification in the attribute information of the business task is replaced with the target data storage specification, while other attributes are fully reused to generate the initial recovery task configuration. Subsequently, a unique identifier is assigned to this initial recovery task (e.g., adding a "-1" suffix to the business task number) and associated with that business task number. Then, the task is registered in the scheduling system and bound to a specified storage medium (e.g., mounted to a specific directory on the host), thus completing the construction of the initial recovery task. Afterwards, migration tools (e.g., the host system's dataset replication tool, cloud storage's cross-container migration interface, etc.) are used to migrate the source data corresponding to the business task to the storage medium associated with the initial recovery task, resulting in the recovery business task. Then, based on historical execution data, the starting execution node of the recovery business task is determined (e.g., if the business task was interrupted in step 4, the recovery business task starts execution from step 4), and processed data segments are skipped (e.g., if the business task has processed the first 100,000 data entries, the recovery business task starts processing directly from entry 100,001). Based on this, the recovery business task is executed by combining the operating parameters and the determined starting node, and its operating information is continuously acquired to determine whether the recovery business task has been interrupted twice, thereby realizing closed-loop monitoring and automatic fault tolerance of the execution process; at the same time, the business task is deleted to release the resources it occupies and avoid resource redundancy.

[0077] In this embodiment, the above steps not only reduce the probability of secondary interruption and achieve self-recovery from interruption, but also allow the recovery business task to continue running from the interruption node and reuse the processed data, avoiding the efficiency loss caused by rerunning the entire process. This saves computing resources and execution time, and reduces resource redundancy and management costs.

[0078] Further, step 215 may specifically include: if the recovery attribute information of the business task is newly created, then generate a recovery business task based on the target data storage specification; and execute the recovery business task based on the job parameters.

[0079] In the specific implementation, after determining that the interruption type is a dataset interruption, if the recovery attribute information of the business task is "new", the attribute information of the business task is reused, but its data storage specification is replaced with the target data storage specification to generate a recovery business task configuration. Subsequently, a unique identifier is assigned to this recovery business task, associated with the business task number, and task registration and storage carrier binding are completed in the scheduling system, thereby constructing a complete recovery business task. Then, the recovery business task is re-executed based on the job parameters to ensure that its processing logic is consistent with the original business task, that is, to execute the entire business process from the initial steps. During execution, its running information is continuously acquired and monitored to determine whether a secondary interruption has occurred, thus achieving closed-loop monitoring and automatic fault tolerance of the recovery process.

[0080] In this embodiment, the above steps not only enable self-recovery after dataset interruption, effectively reducing the probability of secondary interruption, but also significantly shorten the recovery cycle; at the same time, they avoid logical gaps and data inconsistencies that may be caused by reusing some processed data, ensuring the accuracy and reliability of business results.

[0081] Further, step 215 may specifically include: if the recovery attribute information of the business task is to continue writing, then generate a recovery business task based on the target data storage specification; and execute the recovery business task based on the job parameters and the historical operation status of the business task.

[0082] In the specific implementation, after determining that the interruption type is a dataset interruption, if the recovery attribute information of the business task is "new", the attribute information of the business task is reused, but its data storage specification is replaced with the target data storage specification to generate a recovery business task configuration. Subsequently, a unique identifier is assigned to the recovery business task, associated with the business task number, and the task is registered in the scheduling system, binding it to the storage carrier corresponding to the target data storage specification, thereby constructing a complete and independently executable recovery business task.

[0083] Then, based on the historical execution status of the business task, the starting execution node of the recovery business task is determined, and the processed data segments are skipped. On this basis, the recovery business task is executed in combination with the running parameters of the business task and the aforementioned determined starting node, that is, only the remaining process of the business task that has not been completed is executed; during the execution, the running information of the recovery business task is continuously acquired, and it is used to determine whether the recovery business task has been interrupted twice, so as to achieve closed-loop monitoring and automatic fault tolerance of the execution process.

[0084] In this embodiment, the above steps not only enable automatic recovery of the dataset after interruption, effectively reducing the probability of secondary interruption, but also eliminate the need for additional data migration operations, reducing resource consumption and system maintenance costs in intermediate steps; at the same time, they avoid the problems of data duplication or omission, ensuring the accuracy and completeness of the final business results.

[0085] Optionally, if the recovery attribute information of a business task is empty, or its attribute values ​​do not belong to the specified types mentioned above, then after determining that the interruption type is a dataset interruption, the target data storage specification is directly calculated based on the preset expansion coefficient and the data storage specification of the business task. Subsequently, all attribute information of the original business task is reused, and only the data storage specification is replaced with the target data storage specification to generate a recovery business task. Then, the recovery business task is executed using the job parameters of the original business task, while the original business task is deleted and its occupied resources are released, ensuring a closed-loop business process with no resource redundancy.

[0086] Step 216: Obtain full execution information of business tasks.

[0087] Specifically, full runtime information refers to the complete set of runtime data generated throughout the entire process of a business task from startup to interruption. Full runtime information includes complete error logs, resource usage snapshots, business parameter configurations, dependent component status, task execution progress, etc.

[0088] In practice, after determining that the interruption type is not a dataset interruption, the full running information of the business task can be obtained based on the business task's execution log system, resource monitoring platform, and dependent component status interface, thereby providing a data foundation for obtaining subsequent interruption alarm messages.

[0089] Step 217: Encapsulate all running information based on a preset message format to obtain an interruption alarm message.

[0090] Specifically, a preset message format refers to a standardized alarm message structure template defined in advance according to actual conditions or needs. It specifies which fields must be included in an interruption alarm message and the format of these fields. For example, a preset message format may include fields such as task number, interruption time, service type, and alarm level. An interruption alarm message refers to alarm notification data generated after encapsulating all operational information according to the preset message format.

[0091] In practice, the required data can be filtered from the full set of operational information based on a preset message format. Then, the filtered data can be combined according to the preset message format to generate an interruption alarm message. This not only makes the alarm information structure uniform and the key content clear at a glance, greatly improving the reading efficiency of the staff, but also avoids the tediousness of analyzing massive amounts of raw logs one by one, effectively improving the efficiency of fault diagnosis.

[0092] Step 218: Send the interruption alarm message to the staff's terminal.

[0093] Specifically, a terminal refers to the electronic devices used by personnel responsible for the operation and maintenance of business tasks and troubleshooting, such as computers, mobile terminals, tablets, etc.

[0094] In practice, after receiving an interruption alarm message, it can be immediately pushed to the staff's terminal through a preset notification channel (such as email, SMS or system pop-up), thereby ensuring that the staff can intervene and handle the situation as soon as possible, effectively shortening the duration of business interruption.

[0095] The interruption recovery method provided in this invention first obtains the job parameters of the business task to be executed, and then executes the business task based on the job parameters. This achieves standardization and automation of the task and provides a unified data benchmark and basis for subsequent monitoring, diagnosis, and recovery. Next, it obtains the operational information of the business task and determines whether the business task has been interrupted based on the operational information. This enables real-time monitoring and accurate fault detection of the business task, avoiding prolonged business stagnation due to failure to detect interruptions in a timely manner. If no interruption occurs, the operational information of the business task is obtained to monitor the task's progress in real time and predict potential risks promptly. If an interruption occurs, it is determined whether the interruption type is a dataset interruption. If it is not a dataset interruption, the full operational information of the business task is obtained, providing a data foundation for obtaining subsequent interruption alarm messages. Then, the full operational information is encapsulated based on a preset message format to obtain the interruption alarm message. This ensures that the obtained alarm information has a unified structure and key content is readily apparent, improving the reading efficiency of staff and avoiding the tedious process of analyzing massive amounts of raw logs one by one, effectively improving fault diagnosis efficiency. Subsequently, an interruption alarm message is sent to the staff's terminals to ensure that staff can intervene and handle the situation immediately, thereby effectively shortening the duration of business interruption. If the interruption is a dataset, the target data storage specification is determined based on a preset expansion coefficient and the data storage specification of the business task. This allows for rapid determination of the target data storage specification, shortening the recovery time for interruptions caused by data storage problems and improving the efficiency of automated recovery. Simultaneously, it ensures the compatibility of the target data storage specification with the original business task configuration, reducing the risk of failure in restoring the business task. Then, based on the attribute information of the business task and the target data storage specification, a corresponding recovery business task is generated and executed. This achieves automated recovery after a dataset interruption, reducing the cost of manual intervention and the risk of configuration errors, while improving the efficiency and reliability of interruption recovery, thereby ensuring business continuity and system stability, and effectively reducing the probability of secondary interruptions. Therefore, the technical solution of this invention solves the problems of low interruption recovery efficiency, insufficient stability, high labor costs, and inability to adapt to the maintenance needs of large-scale systems caused by reliance on manual operation in existing technologies.

[0096] Figure 3 This is a schematic diagram of an interrupt recovery device provided in an embodiment of the present invention. This device belongs to the same inventive concept as the interrupt recovery methods in the above embodiments. For details not described in detail in the embodiments of the interrupt recovery device, please refer to the embodiments of the above interrupt recovery methods.

[0097] like Figure 3 As shown, the device includes:

[0098] The execution module 310 is used to obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters;

[0099] The judgment module 320 is used to obtain the operation information of the business task and determine whether the business task has been interrupted based on the operation information;

[0100] The determination module 330 is used to determine the target data storage specification based on a preset expansion coefficient and the data storage specification of the business task if the business task is interrupted, and the interruption type is a dataset interruption.

[0101] The recovery module 340 is used to generate a recovery business task corresponding to the business task based on the attribute information of the business task and the target data storage specifications, and to execute the recovery business task.

[0102] Based on the above embodiments, the attribute information includes recovery attribute information, and the recovery module 340 is specifically used for:

[0103] If the recovery attribute information of the business task is migration, an initial recovery task is generated based on the target data storage specification; the source data corresponding to the business task is migrated to the storage carrier associated with the initial recovery task to obtain the recovery business task; the recovery business task is executed based on the job parameters and the historical operation status of the business task, and the business task is deleted.

[0104] Based on the above embodiments, the recovery module 340 is specifically used for:

[0105] If the recovery attribute information of the business task is "new", then the recovery business task is generated based on the target data storage specification; and the recovery business task is executed based on the job parameters.

[0106] Based on the above embodiments, the recovery module 340 is specifically used for:

[0107] If the recovery attribute information of the business task is to continue writing, then the recovery business task is generated based on the target data storage specification; the recovery business task is executed based on the job parameters and the historical operation status of the business task.

[0108] Based on the above embodiments, the device further includes:

[0109] The sending module is used to, after determining whether the business task has been interrupted based on the running information, if the business task has been interrupted, and assuming the interruption type is not a dataset interruption, obtain the full running information of the business task; encapsulate the full running information based on a preset message format to obtain an interruption alarm message; and send the interruption alarm message to the staff's terminal.

[0110] Based on the above embodiments, the determination module 320 determines whether the business task has been interrupted based on the running information, including:

[0111] The return code in the operation information is matched with the preset interrupt code to obtain the matching result; if the matching result is a match, it is determined that the service task has been interrupted.

[0112] The interrupt recovery device provided in the embodiments of the present invention can execute the interrupt recovery method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method.

[0113] It is worth noting that in the above embodiments of the interrupt recovery device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0114] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Figure 4 A block diagram of an exemplary electronic device 4 suitable for implementing embodiments of the present invention is shown. Figure 4 The electronic device 4 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0115] like Figure 4 As shown, electronic device 4 is represented in the form of a general-purpose computing electronic device. The components of electronic device 4 may include, but are not limited to: one or more processors or processing units 16, system memory 28, and bus 18 connecting different system components (including system memory 28 and processing unit 16).

[0116] Bus 18 represents one or more of several bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.

[0117] Electronic device 4 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by electronic device 4, including volatile and non-volatile media, removable and non-removable media.

[0118] System memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Electronic device 4 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 may be used to read and write non-removable, non-volatile magnetic media (… Figure 4 Not shown; usually referred to as a "hard drive"). Although Figure 4 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk") and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 via one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to perform the functions of the embodiments of the present invention.

[0119] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28. Such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. Program modules 42 typically perform the functions and / or methods described in the embodiments of the present invention.

[0120] Electronic device 4 can also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), and with one or more devices that enable a user to interact with electronic device 4, and / or with any device that enables electronic device 4 to communicate with one or more other computing devices (e.g., network card, modem, etc.). This communication can be performed through input / output (I / O) interface 22. Furthermore, electronic device 4 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 20. Figure 4 As shown, network adapter 20 communicates with other modules of electronic device 4 via bus 18. It should be understood that, although... Figure 4 Not shown, it can be combined with electronic device 4 to use other hardware and / or software modules, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0121] Processing unit 16 executes various functional applications and page displays by running programs stored in system memory 28, such as implementing the interrupt recovery method provided in this embodiment of the invention, which includes:

[0122] Obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters;

[0123] Obtain the operation information of the business task, and determine whether the business task has been interrupted based on the operation information;

[0124] If the business task is interrupted, and the interruption type is dataset interruption, the target data storage specification is determined based on the preset expansion coefficient and the data storage specification of the business task.

[0125] Based on the attribute information of the business task and the target data storage specifications, a recovery business task corresponding to the business task is generated and executed.

[0126] Of course, those skilled in the art will understand that the processor can also implement the technical solution of the interrupt recovery method provided in any embodiment of the present invention.

[0127] This invention provides a computer-readable storage medium storing a computer program thereon. When executed by a processor, the program implements, for example, the interrupt recovery method provided in this invention, which includes:

[0128] Obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters;

[0129] Obtain the operation information of the business task, and determine whether the business task has been interrupted based on the operation information;

[0130] If the business task is interrupted, and the interruption type is dataset interruption, the target data storage specification is determined based on the preset expansion coefficient and the data storage specification of the business task.

[0131] Based on the attribute information of the business task and the target data storage specifications, a recovery business task corresponding to the business task is generated and executed.

[0132] The computer storage medium of this invention can be any combination of one or more computer-readable media. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0133] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0134] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0135] Computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0136] Those skilled in the art will understand that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby allowing them to be stored in a storage device for execution by a computing device, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0137] Furthermore, the acquisition, storage, use, and processing of data in the technical solution of this invention all comply with relevant laws and regulations.

[0138] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. An interruption recovery method, characterized in that, The method includes: Obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters; Obtain the operation information of the business task, and determine whether the business task has been interrupted based on the operation information; If the business task is interrupted, and the interruption type is dataset interruption, the target data storage specification is determined based on the preset expansion coefficient and the data storage specification of the business task. Based on the attribute information of the business task and the target data storage specifications, a recovery business task corresponding to the business task is generated and executed.

2. The interruption recovery method according to claim 1, characterized in that, The attribute information includes recovery attribute information. A recovery business task corresponding to the business task is generated based on the attribute information of the business task and the target data storage specifications. The recovery business task is then executed, including: If the recovery attribute information of the business task is migration, then an initial recovery task is generated based on the target data storage specification; The source data corresponding to the business task is migrated to the storage carrier associated with the initial recovery task to obtain the recovery business task; The recovery task is executed based on the job parameters and the historical operation status of the business task, and the business task is then deleted.

3. The interruption recovery method according to claim 2, characterized in that, Based on the attribute information of the business task and the target data storage specifications, a recovery business task corresponding to the business task is generated, and the recovery business task is executed, including: If the recovery attribute information of the business task is "new", then the recovery business task is generated based on the target data storage specification; The recovery task is executed based on the stated job parameters.

4. The interruption recovery method according to claim 2, characterized in that, Based on the attribute information of the business task and the target data storage specifications, a recovery business task corresponding to the business task is generated, and the recovery business task is executed, including: If the recovery attribute information of the business task is continuation, then the recovery business task is generated based on the target data storage specification; The recovery task is executed based on the job parameters and the historical operation data of the business task.

5. The interruption recovery method according to claim 1, characterized in that, After determining whether the business task has been interrupted based on the operational information, the process further includes: If the business task is interrupted, then if the interruption type is not a dataset interruption, then obtain the full running information of the business task. The entire runtime information is encapsulated based on a preset message format to obtain an interruption alarm message; The interruption alarm message is sent to the staff's terminal.

6. The interruption recovery method according to claim 1, characterized in that, Determining whether the business task has been interrupted based on the operational information includes: The return code in the running information is matched with the preset interrupt code to obtain the matching result; If the matching result is a match, then it is determined that the business task has been interrupted.

7. An interrupt recovery device, characterized in that, The device includes: The execution module is used to obtain the job parameters of the business task to be executed, and execute the business task based on the job parameters; The judgment module is used to obtain the operation information of the business task and determine whether the business task has been interrupted based on the operation information; The determination module is used to determine the target data storage specification based on a preset expansion coefficient and the data storage specification of the business task if the business task is interrupted, and the interruption type is a dataset interruption. The recovery module is used to generate a recovery business task corresponding to the business task based on the attribute information of the business task and the target data storage specifications, and to execute the recovery business task.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the interrupt recovery method according to any one of claims 1-6.

9. A storage medium containing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform the interrupt recovery method according to any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the interrupt recovery method according to any one of claims 1-6.

Images