Job management method

Abstract

The invention relates to a job management method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: determining a current job in a job sequence corresponding to a service, and determining an execution strategy of the service based on an attribute relationship among jobs in the service; querying a job execution result of a previous job of the current job, and determining a target correction strategy corresponding to the current job according to the job execution result and the execution strategy; and managing the current job according to the target correction strategy. By adopting the method, the execution success rate of the job can be improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a job management method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] Business needs are divided into multiple business tasks for processing. During the processing of business tasks, the management server pre-stores the business sequence numbers of each business task that needs to be processed in the business. The management server groups each business sequence number according to the preset number of tasks to obtain each business sequence number group, and constructs a job sequence corresponding to the business based on each business sequence number group, so as to batch process the business tasks with the job in the job sequence as the execution unit, thereby speeding up the processing efficiency of the business. The management server manages the job of each business through the job management method.

[0003] In the current job management method, the management server determines the current job in the job sequence according to the time interval between each job, and constructs a job execution request for the current job. Then, the management server sends the job execution request to the business server corresponding to the business, so that the business server executes each business task in the current job based on the job execution request.

[0004] However, the current job management method sends the job execution request of the current job according to the time interval between jobs. It may happen that the current job is started when the previous job of the current job has not been completed, causing the business server to process two jobs in parallel. The two jobs will affect each other, causing errors in the processing of the current job and reducing the success rate of job execution. Summary of the invention

[0005] Based on this, it is necessary to provide a job management method, apparatus, computer equipment, computer-readable storage medium and computer program product to address the above technical issues.

[0006] In a first aspect, the present application provides a job management method, comprising:

[0007] Determine a current job in a job sequence corresponding to a business, and determine an execution strategy for the business based on an attribute relationship between jobs in the business;

[0008] Querying the job execution result of the previous job of the current job, and determining the target correction strategy corresponding to the current job according to the job execution result and the execution strategy;

[0009] The current job is managed according to the target correction strategy.

[0010] In one embodiment, the attribute relationship includes an association relationship and a logical relationship, and determining the execution strategy of the business based on the attribute relationship between the jobs in the business includes:

[0011] If the association relationship does not exist between the operations of the business, determining that the execution strategy of the business is a parallel execution strategy;

[0012] If the association relationship exists between the operations of the business and the logical relationship does not exist, determining that the execution strategy of the business is to abandon the execution strategy;

[0013] If the association relationship and the logical relationship exist between the operations of the business, it is determined that the execution strategy of the business is a queuing execution strategy.

[0014] In one embodiment, determining the target correction strategy corresponding to the current job according to the job execution result and the execution strategy includes:

[0015] If the execution strategy is a parallel execution strategy, determining that the target correction strategy corresponding to the current job is a normal execution strategy;

[0016] If the execution strategy is the abandonment execution strategy and the job execution result is empty, determining that the target correction strategy corresponding to the current job is the first target correction strategy;

[0017] If the execution strategy is the abandonment execution strategy and the job execution result is not empty, determining that the target correction strategy corresponding to the current job is the normal execution strategy;

[0018] If the execution strategy is a queuing execution strategy, the target correction strategy corresponding to the current job is determined according to the job execution result and the result identifier in the queuing execution strategy.

[0019] In one embodiment, the job execution result includes an end status, and determining the target correction strategy corresponding to the current job according to the job execution result and the result identifier in the queuing execution strategy includes:

[0020] If the job execution result is empty, determining that the target correction strategy corresponding to the current job is the second target correction strategy;

[0021] If the job execution result is not empty, the target correction strategy corresponding to the current job is determined based on the result identifier in the queuing execution strategy and the end status.

[0022] In one embodiment, determining the target correction strategy corresponding to the current job based on the result identifier and the end status in the queuing execution strategy includes:

[0023] If the result identifier in the queue execution strategy indicates that the current job does not need the normal execution result of the previous job, determining that the target correction strategy corresponding to the current job is the normal execution strategy;

[0024] If the result identifier indicates that the current job requires the normal execution result of the previous job, determining whether the end status is a normal end;

[0025] If the end state is a normal end, determining that the target correction strategy corresponding to the current job is a normal execution strategy;

[0026] If the end status is an abnormal end, it is determined that the target correction strategy corresponding to the current job is a third target correction strategy.

[0027] In one embodiment, managing the current job according to the target correction strategy includes:

[0028] If the target correction strategy is a normal execution strategy, sending a job execution request corresponding to the current job to a business server corresponding to the business;

[0029] If the target correction strategy is the first target correction strategy, managing the current job and the next job of the current job according to the first target correction strategy;

[0030] If the target correction strategy is the second target correction strategy, managing the current job according to the second target correction strategy and the job execution result;

[0031] If the target correction strategy is the third target correction strategy, the current job and the previous job are managed according to the third target correction strategy and the job execution result.

[0032] In one embodiment, managing the current job and the next job of the current job according to the first target correction strategy includes:

[0033] Determining the next job of the current job in the job sequence;

[0034] Each business sequence number in the current job is updated to the next job to obtain an updated next job, and the current job is deleted from the job sequence.

[0035] In one embodiment, managing the current job according to the second target correction strategy and the job execution result includes:

[0036] Saving the current job to a queue table corresponding to the business;

[0037] When receiving the job execution result of the previous job, determining whether the result identifier in the queuing strategy indicates that the current job requires the normal execution result of the previous job;

[0038] If the result identifier indicates that the current job does not require the normal execution result, sending a job execution request corresponding to the current job to a business server corresponding to the business;

[0039] If the result identifier indicates that the current job requires the normal execution result, the current job or the previous job is managed according to the end status in the job execution result.

[0040] In one embodiment, the job execution result includes the target business sequence number of each target business task that failed to execute, and the managing the current job or the previous job according to the end status in the job execution result includes:

[0041] If the end status in the job execution result is a normal end, sending a job execution request corresponding to the current job to the business server corresponding to the business;

[0042] If the end status in the job execution result is abnormal end, constructing a job re-execution request of the previous job according to each target business sequence number;

[0043] Send the job re-execution request to the business server corresponding to the business.

[0044] In one embodiment, the job execution result includes the target business sequence number of each target business task that failed to execute, and the managing the current job and the previous job according to the third target correction strategy and the job execution result includes:

[0045] Constructing a job re-execution request of the previous job according to each of the target business sequence numbers;

[0046] Sending the job re-execution request to the business server corresponding to the business, and saving the current job to the queue table corresponding to the business;

[0047] A job re-execution result corresponding to the job re-execution request is received, and when the end status in the job re-execution result is a normal end, a job execution request corresponding to the current job is sent to the business server.

[0048] In a second aspect, the present application also provides a job management device, including:

[0049] A determination module, used to determine the current job in the job sequence corresponding to the business, and determine the execution strategy of the business based on the attribute relationship between the jobs in the business;

[0050] A query module, used to query the job execution result of the previous job of the current job, and determine the target correction strategy corresponding to the current job according to the job execution result and the execution strategy;

[0051] A management module is used to manage the current job according to the target correction strategy.

[0052] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0053] Determine a current job in a job sequence corresponding to a business, and determine an execution strategy for the business based on an attribute relationship between jobs in the business;

[0054] Querying the job execution result of the previous job of the current job, and determining the target correction strategy corresponding to the current job according to the job execution result and the execution strategy;

[0055] The current job is managed according to the target correction strategy.

[0056] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0057] Determine a current job in a job sequence corresponding to a business, and determine an execution strategy for the business based on an attribute relationship between jobs in the business;

[0058] Querying the job execution result of the previous job of the current job, and determining the target correction strategy corresponding to the current job according to the job execution result and the execution strategy;

[0059] The current job is managed according to the target correction strategy.

[0060] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0061] Determine a current job in a job sequence corresponding to a business, and determine an execution strategy for the business based on an attribute relationship between jobs in the business;

[0062] Querying the job execution result of the previous job of the current job, and determining the target correction strategy corresponding to the current job according to the job execution result and the execution strategy;

[0063] The current job is managed according to the target correction strategy.

[0064] The above-mentioned job management method, device, computer equipment, computer-readable storage medium and computer program product determine the current job in the job sequence corresponding to the business, and determine the execution strategy of the business based on the attribute relationship between the jobs in the business; query the job execution result of the previous job of the current job, and determine the target correction strategy corresponding to the current job according to the job execution result and the execution strategy; manage the current job according to the target correction strategy. With this method, the execution strategies of various businesses can be clarified through the attribute relationship of the business. Then, based on the job execution result of the previous job and the execution strategy of the business where the current job is located, it is clarified whether the previous job and the current job will affect each other. In the case that the previous job affects the current job, based on the job execution result and the execution strategy, it is realized to determine the target correction strategy corresponding to the current job in different scenarios, and expand the scope of application of the job management method. The execution logic of the current job is adjusted based on the target correction strategy, so as to avoid the previous job affecting the execution of the current job, so that the current job can be executed normally, and the success rate of job execution is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0066] Figure 1 An application environment diagram of a job management method in an embodiment;

[0067] Figure 2 A flowchart of a job management method in one embodiment;

[0068] Figure 3 A schematic diagram of a flow chart for determining an execution strategy in an embodiment;

[0069] Figure 4 A schematic diagram of a process for determining a target correction strategy according to an execution strategy in one embodiment;

[0070] Figure 5It is a flowchart of determining a target correction strategy according to a job execution result when the execution strategy is a discard strategy in one embodiment;

[0071] Figure 6 It is a flowchart of determining a target correction strategy according to a job execution result when the execution strategy is a queuing strategy in one embodiment;

[0072] Figure 7 A schematic diagram of a process for managing a current job according to a target correction strategy in one embodiment;

[0073] Figure 8 A schematic diagram of a process for managing a current job according to a first target correction strategy in an embodiment;

[0074] Fig. 9 A schematic diagram of a process for managing a current job according to a second target correction strategy in one embodiment;

[0075] Fig.10 A schematic diagram of a process for managing a current job according to an end state in one embodiment;

[0076] Fig.11 A schematic diagram of a process for managing a current job according to a third target correction strategy in one embodiment;

[0077] Fig.12 is an execution flow chart of target correction strategies corresponding to different execution strategies in one embodiment;

[0078] Fig.13 is a structural block diagram of a job management device in an embodiment;

[0079] Fig.14 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0080] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0081] The job management method provided in the embodiment of the present application can be applied to Figure 1 In the operation management system 100 shown. The operation management system 100 includes a management server 110 and business servers 120. The management server 110 is used to manage the operations of each business. The business server 120 is used to execute the business tasks corresponding to the business. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0082] In an exemplary embodiment, Figure 2 As shown, a job management method is provided, which is applied to Figure 1 The management server 110 (hereinafter, the reference numeral is omitted, referred to as the management server) in FIG. 1 is used as an example to illustrate the method, which includes the following steps 202 to 206. Among them:

[0083] Step 202, determining the current job in the job sequence corresponding to the business, and determining the execution strategy of the business based on the attribute relationship between the jobs in the business.

[0084] The job sequence includes each job and an execution tag corresponding to each job.

[0085] In implementation, the management server determines the job sequence corresponding to the business, and determines the first job with the execution tag of not executed in the job sequence as the current job. Then, the management server obtains the business information of the business according to the business identifier of the business, and determines the execution strategy of the business according to the attribute relationship of each job in the business information.

[0086] Specifically, the management server needs to manage multiple services. The management server is set with a time interval for each service. For each service, the management server determines the job sequence corresponding to the service according to the time interval corresponding to the service. Then, the management server determines the execution of each job with an execution tag of not executed in the job sequence, and determines the first job as the current job. The management server obtains the business information of the business according to the business identifier of the business, and determines the execution strategy of the business according to the attribute relationship of each job in the business information.

[0087] In an exemplary embodiment, a job management platform is provided on a management server, and the job management platform needs to manage jobs of multiple services. The management server is provided with a service identifier of each service and a time interval corresponding to each service. For each service, the management server determines a start time set corresponding to the service according to the time interval corresponding to the service. For each service, when the current time is a start time in the start time set corresponding to the service, the management server queries the job sequence corresponding to the service according to the service identifier, and determines the first job with an execution tag of not executed in the job sequence as the current job. Then, the management server obtains the service information of the service according to the service identifier, and determines the execution strategy of the service according to the attribute relationship of each job in the service information.

[0088] For example, the business is a transfer business. The management server is set with a time interval corresponding to the transfer business. The management server calculates the startup time set corresponding to the transfer business according to the time interval. When the current time is the startup time in the startup time set, the management server queries the transfer job sequence corresponding to the transfer business according to the transfer business identifier of the transfer business, and determines in the transfer job sequence that the first transfer job with an execution tag of not executed is the current transfer job. Then, the management server obtains the transfer business information of the transfer business according to the transfer business identifier, and determines the execution strategy of the transfer business according to the attribute relationship of each transfer job in the transfer business information.

[0089] In an optional embodiment, the management server obtains a historical processing time data set of each business task in the business, and determines the processing time of the business task based on the historical processing time data set. Then, the management server determines the time interval of the business based on the processing time of the business task and the number of business tasks in the job.

[0090] Specifically, the management server inputs the historical processing time data set into the time prediction model, and predicts the historical processing time data set through the time prediction model to obtain the processing time of the business task. Then, the management server determines the multiplication value of the processing time and the number of business tasks in each job as the time interval of the business.

[0091] Optionally, the management server performs mean processing on each historical processing time in the historical processing time data set to obtain the processing time of the business task. The embodiment of the present application does not limit the technical means for determining the processing time.

[0092] Step 204, query the job execution result of the previous job of the current job, and determine the target correction strategy corresponding to the current job according to the job execution result and the execution strategy.

[0093] In implementation, the management server determines the previous job of the current job in the job sequence and queries the job execution result of the previous job. Then, the management server determines the target correction strategy corresponding to the current job according to the job execution result and the execution strategy.

[0094] Specifically, the execution strategy includes parallel execution strategy, abandonment execution strategy and queue execution strategy. The management server determines the previous job of the current job in the job sequence. Then, the management server queries the job execution result of the previous job according to the job identifier of the previous job. If the previous job has been completed, the business server will return the job execution result of the previous job to the management server. That is, the job execution result of the previous job is stored in the management server, and the management server can query the execution result of the previous job. If the previous job is not completed, the management server does not store the job execution result of the previous job. And the management server cannot query the job execution result of the previous job. Then, the management server determines the target correction strategy of the current job according to the job execution result and the execution strategy. Different job execution results and different execution strategies will result in different target correction strategies.

[0095] Step 206, managing the current job according to the target correction strategy.

[0096] Among them, the target correction strategy includes a normal execution strategy, a first target correction strategy, a second target correction strategy and a third target correction strategy.

[0097] During implementation, the management server performs correction processing on the current job according to the target correction strategy.

[0098] Specifically, if the target correction policy is the normal execution policy, the management server processes the current job according to the normal execution policy. If the target correction policy is the first target correction policy, the management server performs correction processing on the current job and the next job of the current job based on the first target correction policy. If the target correction policy is the second target correction policy, the management server performs correction processing on the previous job, the current job, and the next job of the current job based on the second target correction policy. If the target correction policy is the third target correction policy, the management server performs correction processing on the current job and the next job of the current job based on the third target correction policy.

[0099] In the above-mentioned job management method, the execution strategies of various businesses can be clarified through the attribute relationship of the business. Then, based on the job execution result of the previous job and the execution strategy of the business where the current job is located, it is clarified whether the previous job and the current job will affect each other. In the case that the previous job affects the current job, based on the job execution results and execution strategy, it is possible to determine the target correction strategy corresponding to the current job in different scenarios, thereby expanding the scope of application of the job management method. The execution logic of the current job is adjusted based on the target correction strategy, which avoids the previous job affecting the execution of the current job, enables the current job to be executed normally, and improves the success rate of job execution.

[0100] In an exemplary embodiment, the attribute relationship includes an associative relationship and a logical relationship, such as Figure 3 As shown, the specific process of determining the execution strategy of the business based on the attribute relationship between each job in the business in step 202 includes steps 302 to 306. Among them:

[0101] Step 302: If there is no association relationship between the operations of the business, determine that the execution strategy of the business is a parallel execution strategy.

[0102] In implementation, if there is no association relationship between the various services of the business, it means that the various operations are independent of each other and do not affect each other. The management server determines that the execution strategy of the business is a parallel execution strategy. That is, the management server determines that the various operations of the business can be processed in parallel.

[0103] Specifically, if there is no association relationship between the services, the management server determines that the operations are independent of each other and that the operations can be executed in parallel. Then, the management server determines the parallel strategy as the execution strategy of the service.

[0104] In an exemplary embodiment, the service is an order service. There is no association relationship between the services of the order service. In the case that there is no association relationship between the services of the order service, the management server determines that the execution strategy of the order service is a parallel execution strategy.

[0105] Step 304: If there is an association relationship between the operations of the business and no logical relationship, determine that the execution strategy of the business is to abandon the execution strategy.

[0106] In implementation, if there is an association relationship between the various jobs of the business and no logical relationship, it means that the various jobs will affect each other, but the execution order of the various jobs is not restricted. The management server determines that the execution strategy is a discard execution strategy. The discard execution strategy means that the business processor can only execute one job of the business in the same time period.

[0107] Specifically, if there is an association relationship between the various jobs of the business and no logical relationship, it means that the execution of the previous job will affect the execution of the current job. When the business processor processes multiple jobs at the same time, it will cause job processing errors. Therefore, it is necessary to ensure that only one job can be executed at the same time by abandoning the execution strategy. That is, when there is an association relationship between the various jobs of the business and no logical relationship, the management server determines that the execution strategy of the business is the abandonment execution strategy.

[0108] In an exemplary embodiment, there are many reasons why there is an association relationship between the various jobs of a business but no logical relationship. For example, the current job and the previous job need to use a business data at the same time, and the business data has an exclusive lock. When the previous job processes the business task, it will lock the business data, and the current job will not be able to obtain the business data, causing the execution of the current job to fail. Therefore, when there is an association relationship between the various jobs of a business but no logical relationship, it is necessary to ensure that the business server can only process one job at a time. The management server determines the execution strategy of the business as the abandonment execution strategy.

[0109] For example, the business is a serial number generation business. Both the current job and the previous job need to use the current maximum value of the number segment. When the previous job is executed, the current maximum value of the number segment will be locked by an exclusive lock. If the current job is started at this time, the current job cannot obtain the current maximum value of the number segment, resulting in an error in the current business execution. Or the current maximum value of the number segment is not locked. During the execution of the current job by the business server, the business serial number will be generated according to the current maximum value of the number segment, resulting in duplication of the number segments generated by the current job and the previous job. Therefore, there is an association relationship between the various jobs of the serial number generation business and there is no logical relationship. When there is an association relationship between the various jobs of the serial number generation business and there is no logical relationship, the management server determines that the execution strategy corresponding to the serial number generation business is an abandoned execution strategy.

[0110] Optionally, there are many reasons why the various jobs of a business have or do not have an association relationship, such as resource limitations or other limitations corresponding to the business. Document printing jobs are typical jobs that cannot be executed simultaneously due to resource limitations. However, the order between the various document printing jobs of the document printing business is not restricted. At this time, it is necessary to adopt an abandoned execution strategy to ensure that only one document printing job is in a normal execution state at the same time. The embodiments of the present application do not limit the business jobs and reasons that have an association relationship but no logical relationship.

[0111] Step 306: If there is an association relationship and a logical relationship between the operations of the business, determine that the execution strategy of the business is a queuing execution strategy.

[0112] In implementation, if there is an association and a logical relationship between the various jobs of the business, it means that the execution of the current job is affected by the previous job, and there is a specific execution order between the jobs. Therefore, the management server determines the execution strategy of the business as a queuing execution strategy.

[0113] Specifically, if there is a relationship and a logical relationship between the various jobs of the business, the management server determines that there is a specific execution order between the various jobs. That is, the business server can only execute the current job after the previous job is completed. The management server determines the execution strategy of the business as a queuing execution strategy.

[0114] In an exemplary embodiment, the business is an accounting business. That is, the business server needs to accurately record the current general ledger, and each accounting entry must be accurate to ensure that the last general ledger record is accurate. Therefore, for the accounting business, the accounting operation will form a specific execution order according to the time sequence of the accounting. Therefore, there is an association relationship and a logical relationship between the various operations of the accounting business. If there is an association relationship and a logical relationship between the various operations of the accounting business, the management server determines the execution strategy of the accounting business as a queuing execution strategy.

[0115] Optionally, since there is a dependency between the jobs of the business, the operation of the current job depends on the previous job, so a queuing execution strategy is required to make the jobs in the business execute in a specific order. The business can be but is not limited to an accounting business, and the embodiment of the present application does not limit the accounting business.

[0116] In this embodiment, the execution strategies of various businesses are determined through the association and logical relationships of the businesses, which expands the scope of application of the job management method. At the same time, it is clarified whether the jobs can be executed in parallel, which facilitates the subsequent determination of the target correction strategy corresponding to the current job.

[0117] In an exemplary embodiment, Figure 4 As shown, the specific process of determining the target correction strategy corresponding to the current job according to the job execution result and the execution strategy in step 202 includes steps 402 to 408. Among them:

[0118] Step 402: If the execution strategy is a parallel execution strategy, determine that the target correction strategy corresponding to the current job is a normal execution strategy.

[0119] Among them, the execution strategies include parallel execution strategy, abandonment execution strategy and queue execution strategy.

[0120] In implementation, if the execution strategy is a parallel strategy, the operations representing the business are independent of each other and the business server can execute two or more operations at the same time, that is, the execution result of the previous operation does not affect the execution of the current operation. Therefore, the management server determines that the target correction strategy corresponding to the current operation is a normal execution strategy.

[0121] Specifically, if the execution strategy is a parallel execution strategy, the management server determines that the job execution result of the previous job does not affect the execution of the current job, and determines that the current job passes the job check. Then, the management server determines the normal execution strategy as the target correction strategy for the current job.

[0122] In an exemplary embodiment, the target business is an order business, and the current job is a current order job. The execution strategy corresponding to the order business is a parallel execution strategy. In the case where the execution strategy corresponding to the order business is a parallel execution strategy, the management server determines that each order job of the order business can run in parallel. Then, the management server determines that the job execution result of the previous order job does not affect the execution of the current order job, and determines that the current order job passes the job check. Then, the management server determines the normal execution strategy as the target correction strategy for the current order job.

[0123] Step 404: If the execution strategy is to abandon the execution strategy and the job execution result is empty, determine that the target correction strategy corresponding to the current job is the first target correction strategy.

[0124] In implementation, if the execution strategy is the discard strategy, the management server determines that only one job can be running on the business server, and determines that the previous job will affect the execution of the current job. Therefore, the management server determines whether the job execution result of the previous job is empty, thereby determining whether the previous job is completed. If the job execution result is empty, it indicates that the previous job is not completed, and the management server determines that the target correction strategy corresponding to the current job is the first target correction strategy.

[0125] Specifically, if the execution strategy is a discard strategy, the management server determines that only one job can be in the running state on the business server, and determines that the previous job will affect the running of the current job. Therefore, before the current job is executed, it is necessary to first determine whether the previous job has been completed. If the previous job has been completed, the business server will send the job execution result of the previous job to the management server. The management server receives and saves the job execution result of the previous job. The job execution result of the previous job queried by the management server is not empty. If the previous job has not been completed, there is no job execution result in the management server. The job execution result of the previous job queried by the management server is empty. The management server determines whether the job execution result is empty to determine whether the previous job has been completed. If the job execution result is empty, the previous job has not been completed, and the management server determines that the target correction strategy corresponding to the current job is the first target correction strategy, thereby correcting the current job according to the first target correction strategy.

[0126] In an exemplary embodiment, the business is a sequence number generation business, and the current job is a current sequence number generation job. The execution policy corresponding to the sequence number generation business is a discard execution policy. In the case where the execution policy corresponding to the sequence number generation business is a discard execution policy, the management server determines whether the job execution result of the previous sequence number generation job is empty. If the sequence number execution result of the previous sequence number generation job is empty, the management server determines the first target correction policy as the target correction policy of the current sequence number generation job.

[0127] Step 406: If the execution strategy is to abandon the execution strategy and the job execution result is not empty, determine that the target correction strategy corresponding to the current job is the normal execution strategy.

[0128] In implementation, if the execution strategy is the abandonment strategy and the business execution result is not empty, the management server determines that the previous job has been completed and that the previous job will not affect the execution of the current job. If the previous job does not affect the execution of the current job, the management server determines that the current job passes the job check and determines the normal execution strategy as the target correction strategy corresponding to the current job.

[0129] In an exemplary embodiment, the business is a sequence number generation business, and the current job is the current sequence number generation job. The execution policy corresponding to the sequence number generation business is the abandonment execution policy. When the execution policy corresponding to the sequence number generation business is the abandonment execution policy and the job execution result is not empty, the management server determines that the business server has completed the previous sequence number generation job, and there is no sequence number generation job being executed on the current business server. The management server determines that the previous sequence number generation job will not affect the execution of the current sequence number generation job. When the previous sequence number generation job does not affect the current sequence number generation job, the management server determines that the current sequence number generation job passes the job check, and determines the normal execution policy as the target correction policy corresponding to the current sequence number generation job.

[0130] Step 408: If the execution strategy is a queue execution strategy, determine the target correction strategy corresponding to the current job according to the job execution result and the result identifier in the queue execution strategy.

[0131] The queue execution strategy includes a result identifier, which indicates that the current job requires the normal execution result of the previous job.

[0132] In implementation, if the execution strategy is a queuing strategy, the execution status and execution result of the previous job will affect the current job. The management server determines whether the execution status and execution result of the previous job affect the current job based on the job execution result and result identifier, obtains the impact result, and determines the target correction strategy corresponding to the current job based on the impact result.

[0133] In this embodiment, based on different execution strategies and job execution results, the target correction strategy corresponding to the current job is determined in different scenarios, which expands the scope of application of the job management method. In addition, by determining the target correction strategy, it is convenient to adjust the job logic of the current job, avoiding the previous job affecting the current job, so that the current job can be executed normally, and the success rate of job execution is improved.

[0134] In an exemplary embodiment, the job execution result includes an end status, such as Figure 5As shown, the specific processing of step 408 includes steps 502 to 504. Among them:

[0135] Step 502: If the job execution result is empty, determine that the target correction strategy corresponding to the current job is the second target correction strategy.

[0136] In implementation, if the job execution result is empty, the management server determines that the previous job has not been completed, determines that the execution status of the previous job will affect the execution of the current job, and determines that the current job has not passed the job check. If the current job has not passed the job check, it indicates that the current job cannot be started normally according to the normal execution strategy, and the current job needs to be corrected. Then, the management server determines that the target correction strategy corresponding to the current job is the second target correction strategy.

[0137] In an exemplary embodiment, the target business is an accounting business, the previous job is the previous accounting job, and the current job is the current accounting job. If the job execution result of the previous accounting job is empty, the management server determines that the previous execution job has not been completed. To avoid an execution error of the current accounting job, the management server determines that the current accounting job has not passed the inspection, and determines that the target correction strategy corresponding to the current accounting job is the second target correction strategy.

[0138] Step 504: If the job execution result is not empty, determine the target correction strategy corresponding to the current job based on the result identifier and the end status in the queue execution strategy.

[0139] In implementation, if the job execution result is not empty, the management server determines the result identifier of the business in the queue execution strategy corresponding to the business, and determines whether the execution result of the previous job affects the current job based on the result identifier of the business, and obtains the impact result. Then, the management server determines the target correction strategy corresponding to the current job based on the impact result and the execution status of the previous job.

[0140] In this embodiment, whether the previous job is completed is determined by whether the job execution result is empty, thereby clarifying whether the previous job affects the current job. Then, different target correction strategies are determined according to different impact results, covering the execution strategies of the current job in different scenarios, and expanding the scope of use of the job management method.

[0141] In an exemplary embodiment, Figure 6 As shown, the specific processing of step 504 includes steps 602 to 608. Among them:

[0142] Step 602: If the result identifier in the queue execution strategy indicates that the execution result of the previous job does not affect the current job, determine that the target correction strategy corresponding to the current job is a normal execution strategy.

[0143] In implementation, if the result identifier in the queue execution strategy indicates that the current job does not need the normal execution result of the previous job, the management server determines that the current job passes the job check. Then, the management server determines the target correction strategy corresponding to the current job as the normal execution strategy.

[0144] In an exemplary embodiment, the business is a transfer business, the current job is the current transfer job, and the previous job is the previous transfer job. The result indicator in the queuing strategy corresponding to the transfer business indicates that the execution result of the previous transfer job does not affect the current transfer job. The management server determines that the current transfer job passes the job check, and determines that the target correction strategy corresponding to the current transfer job is a normal execution strategy, thereby starting to execute the current transfer job through the normal execution strategy.

[0145] Step 604: If the result identifier indicates that the execution result of the previous job affects the current job, it is determined whether the end status is a normal end.

[0146] In implementation, if the result identifier indicates that the execution result of the previous job affects the current job, the current job can only be executed after the previous job is executed normally. Therefore, the management server determines the end status of the previous job in the job execution result of the previous job and determines whether the end status is a normal end.

[0147] Specifically, in the process of executing the previous job by the business server, there are two situations, including that all business tasks are executed normally and that there are two situations in which the target business task is executed abnormally. The two situations will obtain different job execution results and different execution statuses. Specifically, if there is an abnormal execution of the target business task, the business server will return the information of the abnormal execution of the target business task to the management server. The management server sends the information of stopping execution to the business server. The business server receives the information of stopping execution and stops executing the previous job. Then, the business server constructs the job execution result of the previous job according to the target business sequence number of the target business task that failed to execute, the information that the end status is abnormal end, and the reason for abnormal end, and returns the job execution result of the previous job to the business server. If there is no abnormal execution of the business task, the management server constructs the job execution result of the previous job according to the information that the end status is abnormal end, and returns the job execution result of the previous job to the business server. Therefore, if the result identifier indicates that the execution result of the previous job affects the current job, the management server determines whether the end status in the job execution result is a normal end to determine whether a normal execution result is obtained after the previous job is executed.

[0148] In an exemplary embodiment, the business is an accounting business, the current job is a current accounting job, and the previous job is a previous accounting job. If the result identifier indicates that the execution result of the previous accounting job affects the current job, the management server determines the end status of the previous accounting job in the job execution result of the previous accounting job. Then, the management server determines whether the end status is a normal end. If the end status is a normal end, it indicates that a normal execution result is obtained after the previous accounting job is executed. If the end status is an abnormal end, it indicates that an abnormal execution result is obtained after the previous accounting job is executed.

[0149] Step 606, if the end status is a normal end, determine that the target correction strategy corresponding to the current job is a normal execution strategy.

[0150] In implementation, if the end status is normal end, it indicates that the current job has passed the job check and needs to be started for execution. Therefore, the management server determines the normal execution strategy as the target correction strategy corresponding to the current job.

[0151] In an exemplary embodiment, the current job is a current accounting job. If the end status is normal end, it indicates that the current accounting job has passed the job check. Then, the management server determines the normal execution strategy as the target correction strategy corresponding to the current job to start executing the current accounting job normally.

[0152] Step 608: If the end status is an abnormal end, determine that the target correction strategy corresponding to the current job is the third target correction strategy.

[0153] In implementation, if the end status is abnormal end, it indicates that the current job has not passed the job check and needs to be corrected. Therefore, the management server determines that the target correction strategy corresponding to the current job is the third target correction strategy.

[0154] In an exemplary embodiment, the current job is a current accounting job. If the end status is abnormal end, the management server determines that the current job has not passed the job check. Then, the management server determines the third target correction policy as the target correction policy corresponding to the current job to perform correction processing on the current accounting job.

[0155] In this embodiment, the target correction strategy corresponding to the current job is determined by the result identifier and the end status in the job execution result, which clarifies whether the previous job affects the current job, and obtains different target correction strategies based on different impact results. The execution logic of the current job is corrected through the target correction strategy, which prevents the previous job from affecting the current job in different scenarios, enables the current job to be executed normally, and improves the job execution success rate.

[0156] In an exemplary embodiment, Figure 7 As shown, the specific processing of step 206 includes steps 702 to 708. Among them:

[0157] Step 702: If the target correction policy is a normal execution policy, a job execution request corresponding to the current job is sent to a business server corresponding to the business.

[0158] In implementation, the management server and the business server are connected via a network. If the target correction policy is a normal execution policy, the management server constructs a job execution request corresponding to the current job based on the business identifier of the business and the information of the current job. Then, the management server sends the job execution request corresponding to the current job to the business server via the network connection.

[0159] Specifically, if the target correction policy is the normal execution policy, the management server constructs a job execution request corresponding to the current job according to the business identifier of the business and the job information of the current job. The management server sends the job execution request to the business server corresponding to the business according to the business identifier. The business server receives the job execution request and executes each business task corresponding to each business sequence according to each business sequence number in the job execution request.

[0160] In an exemplary embodiment, the business is an order business. The current job is a current order job. If the target correction strategy is a normal execution strategy, the management server constructs a job execution request corresponding to the current order job according to the order business identifier of the order business and the job information of the current order job. Then, the management server sends the job execution request to the business server corresponding to the order business according to the order business identifier. The business server receives the job execution request corresponding to the current order job. Then, the business server executes each order business task in the current order job according to each business sequence number in the job execution request.

[0161] Optionally, the normal execution strategy can be applied to, but is not limited to, order services, accounting services, etc. The embodiments of the present application do not limit the services to which the normal execution strategy is applied.

[0162] Step 704: If the target correction strategy is the first target correction strategy, the current job and the next job of the current job are managed according to the first target correction strategy.

[0163] In implementation, if the target correction policy is the first target correction policy, the management server determines the next job in the job sequence and performs correction processing on the current job and the next job according to the first target correction policy.

[0164] Specifically, if the target revision policy is the first target revision policy, the management server determines the next job of the current job, updates the next job according to the first target revision policy and the current job, and deletes the current job.

[0165] Step 706: If the target correction strategy is the second target correction strategy, manage the current job according to the second target correction strategy and the job execution result.

[0166] In implementation, if the target correction strategy is the second target correction strategy, the management server saves the current job into the queue table corresponding to the business, and corrects the current job according to the result identifier in the queue strategy and the job execution result.

[0167] Step 708: If the target correction strategy is the third target correction strategy, the current job and the previous job are managed according to the third target correction strategy and the job execution result.

[0168] The job execution result includes the target business sequence number of each target business task that failed to execute.

[0169] In implementation, if the target correction strategy is the third target correction strategy, the management server corrects the current job according to the third correction strategy. At the same time, the management server corrects the previous job according to each target business sequence number.

[0170] In this embodiment, different target correction strategies are used to correct the current job in different application scenarios, thereby avoiding the current job from being affected by the previous job, ensuring that the current job can be successfully executed, and improving the success rate of job execution.

[0171] In an exemplary embodiment, Figure 8 As shown, the specific process of managing the current job and the next job of the current job according to the first target correction strategy in step 704 includes steps 802 to 804. Among them:

[0172] Step 802, determining the next job of the current job in the job sequence.

[0173] In implementation, the management server determines the next job of the current job in the job sequence according to the order of the job sequence.

[0174] In an exemplary embodiment, the job sequence is a sequence of sequence generation jobs corresponding to a sequence generation service. The management server determines the next sequence generation job of the current sequence generation job in the sequence of sequence generation jobs as the next sequence generation job.

[0175] Step 804, update each business sequence number in the current job to the next job, obtain the updated next job, and delete the current job in the job sequence.

[0176] In implementation, the management server determines each business sequence number in the current job. The business sequence number is the task identifier of each business task to be executed in the current job. The management server adds each business sequence number to the next business to obtain the updated next job. Then, the management server deletes the current sequence in the job sequence.

[0177] Specifically, the management server determines the service sequence number of each job in the current job, and adds each service sequence number to the next job to obtain the updated next job. Then, the management server deletes the current sequence in the job sequence. When the current time is the start time of the next job, the management server determines the next job as the current job, and executes the steps of determining the execution strategy of the business based on the attribute relationship between the jobs in the business, until all jobs in the job sequence are executed.

[0178] In an exemplary embodiment, the business is a sequence generation business, the current job is the current sequence generation job, and the next job is the next sequence generation job. The time interval of the sequence generation business is 3 minutes, and the start time of the sequence generation business is 09:00:00 on September 18, 2024. The management server executes the job management method every 3 minutes starting from 09:00:00 on September 18, 2024. Specifically, when the current time is 09:03:00 on September 18, 2024, the management server determines that the current time reaches the start time of the sequence generation job. The management server determines the current sequence generation job in the sequence generation job sequence corresponding to the sequence generation business, and determines that the execution strategy of the sequence generation business is the abandonment execution strategy based on the attribute relationship between each job in the sequence generation business. The management server queries the job execution result of the previous sequence generation job of the current sequence generation job. If the job execution result is empty, the management server determines that the target correction strategy of the current sequence generation job is the first target correction strategy. Then, the management server determines the next sequence number generation job in the sequence of sequence number generation jobs based on the first target correction strategy, and adds each business sequence number in the current sequence number generation job to the next sequence number generation job to obtain the updated next sequence number generation job. When the current time is 09:06:00 on September 18, 2024, the management server determines that the current time reaches the start time. The management server determines the updated next sequence number generation job as the current sequence number generation job. Then, the management server determines that the execution strategy of the sequence number generation business is the abandonment execution strategy based on the attribute relationship between each job in the sequence number generation business. The management server queries the job execution result of the previous sequence number generation job of the current sequence number generation job. If the job execution result is not empty, the management server determines that the target correction strategy of the current sequence number generation job is a normal execution strategy. The management server sends a job execution request of the current sequence number generation job to the business server corresponding to the sequence number generation business according to the normal execution strategy, so that the business server executes the current sequence number generation job, thereby generating each business sequence number.

[0179] In this embodiment, each business sequence number in the current job is added to the next job through the first target execution strategy, and the current job is deleted, so that the business server can execute each business task in the current job when executing the next job, avoiding the operation of the previous job affecting the current job and improving the success rate of job execution.

[0180] In an exemplary embodiment, Fig. 9 As shown, the specific process of managing the current job according to the second target correction strategy and the job execution result in step 706 includes steps 902 to 908. Among them:

[0181] Step 902: Save the current job to the queue table corresponding to the business.

[0182] In implementation, a queue table corresponding to each service is pre-set in the management server. The management server saves the current job into the queue table corresponding to the service. The queue table is used to store unexecuted jobs.

[0183] Specifically, if the execution strategy corresponding to the business is a queuing strategy, the management server initializes the queuing table to store unexecuted jobs. The management server saves the current job in the queuing table corresponding to the business. The queuing form of each job in the queuing table is a hand-in-hand mode, and the current job in the queuing table will be associated with the job identifier of the previous job. When the previous job is completed, the management server will immediately start the execution of the current job. For example, there is a queuing sequence A{A1, A2, A3, An} in the queuing table. When the A1 job is executed, the management server immediately pulls up the A2 job. After A2 completes the job, the management server pulls up A3. After A3 is completed, it pulls up An.

[0184] In an optional embodiment, the capacity of the queue table is limited. If the queue table is full, the management server abandons the current job and determines the next job as the current job. Then, the management server performs the step of determining the execution strategy of the business based on the attribute relationship between the jobs in the business until all jobs in the job sequence are executed.

[0185] Optionally, the capacity of the queue table is determined according to the data size of each job in the business and the queue demand. The embodiment of the present application does not limit the queue capacity.

[0186] Step 904: when the job execution result of the previous job is received, it is determined whether the result identifier in the queuing strategy indicates that the current job requires the normal execution result of the previous job.

[0187] The queuing strategy includes a result identifier.

[0188] In implementation, when receiving the job execution result of the previous job, the management server determines whether the result identifier indicates that the current job requires the normal execution result of the previous job. If the result identifier indicates that the current job does not require the normal execution result of the previous job, step 906 is executed; if the result identifier indicates that the normal execution result of the previous job of the current job sequence number is executed, step 908 is executed.

[0189] Step 906: If the result identifier indicates that the current job does not require a normal execution result, a job execution request corresponding to the current job is sent to a business server corresponding to the business.

[0190] In implementation, if the result identifier indicates that the current job does not require the normal execution result of the previous job, the management server sends a job execution request corresponding to the current job to the business server corresponding to the business. The specific process of sending the job execution request corresponding to the current job has been described in the embodiment of step 702 above, and the embodiment of this application will not be repeated here.

[0191] Step 908: If the result identifier indicates that the current job needs a normal execution result, the current job or the previous job is managed according to the end status in the job execution result.

[0192] The job execution result includes an end status.

[0193] In implementation, if the result identifier indicates that the current job needs a normal execution result, the management server determines whether the end status is a normal end. If the end status is a normal end, the management server manages the current job. If the end status is an abnormal end, the management server corrects the previous job.

[0194] In this embodiment, when the execution strategy is a queuing strategy and the job execution result of the previous job has not been received, the current job is saved in the queuing table. Then, when the job result of the current job is received, the previous job and the current job are corrected according to the job execution result and the end status, ensuring that the previous job does not affect the execution of the current job and improving the success rate of job execution.

[0195] In an exemplary embodiment, Fig.10 As shown, the job execution result includes the target business serial number of each target business task that failed to execute, and the specific processing of managing the current job or the previous job according to the end status in the job execution result in step 908 includes steps 1002 to 1006. Among them:

[0196] Step 1002: If the end status in the job execution result is normal end, a job execution request corresponding to the current job is sent to a business server corresponding to the business.

[0197] In implementation, if the end status in the job execution result is normal end, the management server sends a job execution request corresponding to the current job to the business server corresponding to the business. The specific process of sending the job execution request corresponding to the current job has been described in the above step 702, and the embodiment of the present application will not be repeated here.

[0198] Step 1004: If the end status in the job execution result is abnormal end, a job re-execution request of the previous job is constructed according to each target business sequence number.

[0199] In implementation, if the end status in the job execution result is an abnormal end, the management server constructs a job re-execution request for the previous job according to the target service sequence number and the service identifier of the service.

[0200] Step 1006: Send a job re-execution request to the business server corresponding to the business.

[0201] In implementation, the management server sends a job re-execution request of the previous job to the business server corresponding to the business according to the business identifier. The business server receives the job re-execution request of the previous job. Then, the business server re-executes each target business task corresponding to each target business sequence number according to the job re-execution request of the previous job.

[0202] In an exemplary embodiment, the business is an accounting business. The current job is a current accounting job. If the end status in the job execution result is an abnormal end, the management server determines that the previous job will affect the execution of the current job, and the previous accounting job needs to be re-executed. Therefore, the management server constructs a job re-execution request for the previous accounting job according to the target business sequence numbers in the previous job and the business identifier of the accounting business. Then, the management server sends the job re-execution request for the previous accounting job to the business server corresponding to the accounting business. The business server receives the job re-execution request for the previous accounting job, and executes each target business task according to each target business sequence number in the job re-execution request. Then, the business server sends the job re-execution result of the job re-execution request to the management server. If the end status in the job re-execution result is a normal end, the management server determines the current accounting job in the queue table, and sends the job execution request corresponding to the current accounting job to the business server corresponding to the accounting business, so that the business server starts to execute the current accounting job.

[0203] In this embodiment, different correction processing is performed on the current job or the previous job based on the end status in the job execution result of the previous job, so that the previous job does not affect the execution of the current job, ensuring that the current job can be successfully executed, and improving the success rate of job execution.

[0204] In an exemplary embodiment, Fig.11 As shown, the job execution result includes the target business serial number of each target business task that failed to execute, and the specific processing of managing the current job and the previous job according to the third target correction strategy and the job execution result in step 708 includes steps 1102 to 1106. Among them:

[0205] Step 1102: construct a job re-execution request for the previous job according to the sequence number of each target business.

[0206] In implementation, the management server constructs a job re-execution request of the previous job according to the target business sequence number of each target business task and the business identifier of the business.

[0207] Step 1104: Send the job re-execution request to the business server corresponding to the business, and save the current job into the queue table corresponding to the business.

[0208] In implementation, the management server sends the job re-execution request of the previous job to the business server corresponding to the business according to the business identifier. At the same time, the management server saves the current job into the queue table corresponding to the business. The specific process of the management server saving the current job into the queue table has been described in the embodiment of the above steps, and the embodiment of the present application will not be repeated here.

[0209] Step 1106, receiving the job re-execution result corresponding to the job re-execution request, and when the end status in the job re-execution result is a normal end, sending the job execution request corresponding to the current job to the business server.

[0210] In implementation, the business server re-executes the target business task corresponding to each target business sequence number according to the job re-execution request, and obtains the job re-execution result. Then, the business server sends the job re-execution result corresponding to the job re-execution request to the management server. The management server receives the job re-execution result corresponding to the job re-execution request. Then, the management server determines whether the end status in the job re-execution result is a normal result. If the end status in the job re-execution result is a normal end, the management server sends the job execution request corresponding to the current job to the business server.

[0211] In this embodiment, by sending a job re-execution request of the previous job to the business server, the business server re-executes the target business tasks in the previous job, and when the end status in the job re-execution result is normal end, the current job is started to be executed, ensuring that the current job is not affected by the previous job, thereby improving the success rate of job execution.

[0212] In an exemplary embodiment, Fig.12 The execution flow chart of the target modification strategy corresponding to different execution strategies. Fig.12As shown, the business is business A, and the job execution queue of business A includes jobs A1, A2, to An. If the execution strategy corresponding to business A is a parallel execution strategy, it means that when job A1 is not completed, job A2 can be started, so that the business server executes jobs A1 and A2 in parallel. If the execution strategy corresponding to business A is a discard execution strategy, it means that when job A1 is not completed, job A2 cannot be started. The management server needs to add each business sequence number in job A2 to job A3 and discard job A2. If the execution strategy corresponding to business A is a discard execution strategy, it means that when job A1 is not completed, job A2 cannot be started, and jobs A1, A2, to An need to be executed one by one in a specific order. Therefore, the management server saves job A2 in the queue table and executes job A2 when job A1 is completed.

[0213] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0214] Based on the same inventive concept, the embodiment of the present application also provides a job management device for implementing the job management method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more job management device embodiments provided below can refer to the limitations of the job management method above, and will not be repeated here.

[0215] In an exemplary embodiment, Fig.13 As shown, a job management device 1300 is provided, including: a determination module 1301, a query module 1302, and a management module 1303, wherein:

[0216] The determination module 1301 is used to determine the current job in the job sequence corresponding to the business, and determine the execution strategy of the business based on the attribute relationship between the jobs in the business.

[0217] The query module 1302 is used to query the job execution result of the previous job of the current job, and determine the target correction strategy corresponding to the current job according to the job execution result and the execution strategy.

[0218] The management module 1303 is used to manage the current job according to the target correction strategy.

[0219] In an exemplary embodiment, the attribute relationship includes an association relationship and a logical relationship, and the determination module 1301 includes a first determination submodule and a second determination submodule. The second determination submodule includes:

[0220] The third determination submodule is used to determine that the execution strategy of the business is a parallel execution strategy if there is no association relationship between the operations of the business.

[0221] The fourth determination submodule is used to determine that the execution strategy of the business is to abandon the execution strategy if there is an association relationship but no logical relationship between the operations of the business.

[0222] The fifth determining submodule is used to determine that the execution strategy of the business is a queuing execution strategy if there is an association relationship and a logical relationship between the operations of the business.

[0223] In an exemplary embodiment, the query module 1302 includes a first query submodule and a sixth determination submodule. The sixth determination submodule includes:

[0224] The seventh determination submodule is used to determine that the target correction strategy corresponding to the current job is a normal execution strategy if the execution strategy is a parallel execution strategy.

[0225] The eighth determination submodule is used to determine that the target correction strategy corresponding to the current job is the first target correction strategy if the execution strategy is to abandon the execution strategy and the job execution result is empty.

[0226] The ninth determination submodule is used to determine that the target correction strategy corresponding to the current job is a normal execution strategy if the execution strategy is to abandon the execution strategy and the job execution result is not empty.

[0227] The tenth determination submodule is used to determine the target correction strategy corresponding to the current job according to the job execution result and the result identifier in the queue execution strategy if the execution strategy is a queue execution strategy.

[0228] In an exemplary embodiment, the job execution result includes an end status, and the tenth determination submodule includes:

[0229] The eleventh determination submodule is used to determine that the target correction strategy corresponding to the current job is the second target correction strategy if the job execution result is empty.

[0230] The twelfth determination submodule is used to determine the target correction strategy corresponding to the current job based on the result identifier and the end status in the queuing execution strategy if the job execution result is not empty.

[0231] In an exemplary embodiment, the twelfth determining submodule includes:

[0232] The thirteenth determination submodule is used to determine that the target correction strategy corresponding to the current job is a normal execution strategy if the result identifier in the queuing execution strategy indicates that the current job does not need the normal execution result of the previous job.

[0233] The first judgment submodule is used to judge whether the end status is a normal end if the result identifier indicates that the current job requires the normal execution result of the previous job.

[0234] The fourteenth determination submodule is used to determine that the target correction strategy corresponding to the current job is a normal execution strategy if the end status is a normal end.

[0235] The fifteenth determination submodule is used to determine that the target correction strategy corresponding to the current job is the third target correction strategy if the end status is an abnormal end.

[0236] In an exemplary embodiment, the management module 1303 includes:

[0237] The first sending submodule is used to send a job execution request corresponding to the current job to the business server corresponding to the business if the target correction strategy is the normal execution strategy.

[0238] The first management submodule is used to manage the current job and the next job of the current job according to the first target correction strategy if the target correction strategy is the first target correction strategy.

[0239] The second management submodule is used to manage the current job according to the second target correction strategy and the job execution result if the target correction strategy is the second target correction strategy.

[0240] The third management submodule is used to manage the current job and the previous job according to the third target correction strategy and the job execution result if the target correction strategy is the third target correction strategy.

[0241] In an exemplary embodiment, the first management submodule includes:

[0242] The sixteenth determination submodule is used to determine the next job of the current job in the job sequence.

[0243] The first updating submodule is used to update each business sequence number in the current job to the next job, obtain the updated next job, and delete the current job in the job sequence.

[0244] In an exemplary embodiment, the second management submodule includes:

[0245] The first saving submodule is used to save the current job into the queue table corresponding to the business.

[0246] The second judgment submodule is used to judge whether the result identifier in the queuing strategy indicates that the current job requires the normal execution result of the previous job when receiving the job execution result of the previous job.

[0247] The second sending submodule is configured to send a job execution request corresponding to the current job to a business server corresponding to the business if the result identifier indicates that the current job does not require a normal execution result.

[0248] The fourth management submodule is used to manage the current job or the previous job according to the end status in the job execution result if the result identifier indicates that the current job needs a normal execution result.

[0249] In an exemplary embodiment, the job execution result includes the target business serial number of each target business task that failed to execute, and the fourth management submodule includes:

[0250] The third sending submodule is used to send a job execution request corresponding to the current job to the business server corresponding to the business if the end status in the job execution result is a normal end.

[0251] The first construction submodule is used to construct a job re-execution request of the previous job according to each target business sequence number if the end status in the job execution result is an abnormal end.

[0252] The fourth sending submodule is used to send a job re-execution request to a business server corresponding to the business.

[0253] In an exemplary embodiment, the job execution result includes the target business serial number of each target business task that failed to execute, and the third management submodule includes:

[0254] The second construction submodule is used to construct a job re-execution request of the previous job according to each target business sequence number.

[0255] The fifth sending submodule is used to send the job re-execution request to the business server corresponding to the business, and save the current job in the queuing table corresponding to the business.

[0256] The sixth sending submodule is used to receive the job re-execution result corresponding to the job re-execution request, and when the end status in the job re-execution result is a normal end, send the job execution request corresponding to the current job to the business server.

[0257] Each module in the above-mentioned operation management device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0258] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.14 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data used in the job management method. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a job management method is implemented.

[0259] Those skilled in the art will understand that Fig.14 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0260] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0261] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0262] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0263] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0264] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0265] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for operation management, characterized in that: The method comprises: Determine a current job in a job sequence corresponding to a business, and determine an execution strategy for the business based on an attribute relationship between jobs in the business; Querying the job execution result of the previous job of the current job, and determining the target correction strategy corresponding to the current job according to the job execution result and the execution strategy; The current job is managed according to the target correction strategy.

2. The method according to claim 1, characterized in that The attribute relationship includes an association relationship and a logical relationship. The determining of the execution strategy of the business based on the attribute relationship between the jobs in the business includes: If the association relationship does not exist between the operations of the business, determining that the execution strategy of the business is a parallel execution strategy; If the association relationship exists between the operations of the business and the logical relationship does not exist, determining that the execution strategy of the business is to abandon the execution strategy; If the association relationship and the logical relationship exist between the operations of the business, it is determined that the execution strategy of the business is a queuing execution strategy.

3. The method according to claim 1, characterized in that The step of determining the target correction strategy corresponding to the current job according to the job execution result and the execution strategy includes: If the execution strategy is a parallel execution strategy, determining that the target correction strategy corresponding to the current job is a normal execution strategy; If the execution strategy is the abandonment execution strategy and the job execution result is empty, determining that the target correction strategy corresponding to the current job is the first target correction strategy; If the execution strategy is the abandonment execution strategy and the job execution result is not empty, determining that the target correction strategy corresponding to the current job is the normal execution strategy; If the execution strategy is a queuing execution strategy, the target correction strategy corresponding to the current job is determined according to the job execution result and the result identifier in the queuing execution strategy.

4. The method according to claim 3, characterized in that The job execution result includes an end status, and determining the target correction strategy corresponding to the current job according to the job execution result and the result identifier in the queuing execution strategy includes: If the job execution result is empty, determining that the target correction strategy corresponding to the current job is the second target correction strategy; If the job execution result is not empty, the target correction strategy corresponding to the current job is determined based on the result identifier in the queuing execution strategy and the end status.

5. The method according to claim 4, characterized in that The determining the target correction strategy corresponding to the current job based on the result identifier in the queuing execution strategy and the end state includes: If the result identifier in the queue execution strategy indicates that the execution result of the previous job does not affect the current job, determining that the target correction strategy corresponding to the current job is a normal execution strategy; If the result identifier indicates that the execution result of the previous job affects the current job, determining whether the end status is a normal end; If the end state is a normal end, determining that the target correction strategy corresponding to the current job is a normal execution strategy; If the end status is an abnormal end, it is determined that the target correction strategy corresponding to the current job is a third target correction strategy.

6. The method according to claim 1, characterized in that The managing the current job according to the target correction strategy includes: If the target correction strategy is a normal execution strategy, sending a job execution request corresponding to the current job to a business server corresponding to the business; If the target correction strategy is the first target correction strategy, managing the current job and the next job of the current job according to the first target correction strategy; If the target correction strategy is the second target correction strategy, managing the current job according to the second target correction strategy and the job execution result; If the target correction strategy is the third target correction strategy, the current job and the previous job are managed according to the third target correction strategy and the job execution result.

7. The method according to claim 6, characterized in that: The managing the current job and the next job of the current job according to the first target correction strategy includes: Determining the next job of the current job in the job sequence; Each business sequence number in the current job is updated to the next job to obtain an updated next job, and the current job is deleted from the job sequence.

8. The method according to claim 6, characterized in that The managing the current job according to the second target correction strategy and the job execution result includes: Saving the current job to a queue table corresponding to the business; When receiving the job execution result of the previous job, determining whether the result identifier in the queuing strategy indicates that the current job requires the normal execution result of the previous job; If the result identifier indicates that the current job does not require the normal execution result, sending a job execution request corresponding to the current job to a business server corresponding to the business; If the result identifier indicates that the current job requires the normal execution result, the current job or the previous job is managed according to the end status in the job execution result.

9. The method according to claim 8, characterized in that The job execution result includes the target business sequence number of each target business task that failed to execute, and the managing the current job or the previous job according to the end status in the job execution result includes: If the end status in the job execution result is a normal end, sending a job execution request corresponding to the current job to the business server corresponding to the business; If the end status in the job execution result is abnormal end, constructing a job re-execution request of the previous job according to each target business sequence number; Send the job re-execution request to the business server corresponding to the business.

10. The method according to claim 6, characterized in that The job execution result includes the target business sequence number of each target business task that failed to execute, and the managing the current job and the previous job according to the third target correction strategy and the job execution result includes: Constructing a job re-execution request of the previous job according to each of the target business sequence numbers; Sending the job re-execution request to the business server corresponding to the business, and saving the current job to the queue table corresponding to the business; A job re-execution result corresponding to the job re-execution request is received, and when the end status in the job re-execution result is a normal end, a job execution request corresponding to the current job is sent to the business server.

Images