WO2023185137A1 - Procédé et appareil de gestion de tâches, et dispositif et support de stockage - Google Patents

Procédé et appareil de gestion de tâches, et dispositif et support de stockage Download PDF

Info

Publication number
WO2023185137A1
WO2023185137A1 PCT/CN2022/141660 CN2022141660W WO2023185137A1 WO 2023185137 A1 WO2023185137 A1 WO 2023185137A1 CN 2022141660 W CN2022141660 W CN 2022141660W WO 2023185137 A1 WO2023185137 A1 WO 2023185137A1
Authority
WO
WIPO (PCT)
Prior art keywords
task
subtask
executed
target
parameter object
Prior art date
Application number
PCT/CN2022/141660
Other languages
English (en)
Chinese (zh)
Inventor
张德波
刘茂扬
Original Assignee
苏州浪潮智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 苏州浪潮智能科技有限公司 filed Critical 苏州浪潮智能科技有限公司
Publication of WO2023185137A1 publication Critical patent/WO2023185137A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4812—Task transfer initiation or dispatching by interrupt, e.g. masked
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5017—Task decomposition

Definitions

  • the present application relates to the field of task management, and in particular to a task management method, device, equipment and storage medium.
  • pod consists of a group of containers. When the pod is rebuilt, all the containers will be rebuilt, and the processes in the corresponding containers will also be closed and reopened.
  • an important feature of pod is that, It may be rebuilt at any time, causing the services running on it to be interrupted at any time. Therefore, if an application uses pod mode to run on Kubernetes, one issue it must consider is whether its business will be interrupted if the pod is suddenly rebuilt, and whether it will cause garbage data and other problems, especially in the face of long-term tasks, reducing Improve the efficiency of long-term task execution.
  • the purpose of this application is to provide a task management method, device, equipment and medium that can improve task execution efficiency.
  • the specific plan is as follows:
  • this application discloses a task management method, including:
  • the parameter object is read to determine the target subtask being executed when the process was interrupted, and the target subtask is re-executed to resume the task process.
  • the target execution task after dividing the target execution task to obtain a corresponding number of subtasks, it also includes:
  • each subtask corresponds to a parameter value.
  • a task process is launched to perform subtasks including:
  • the filter uses the filter to filter out the subtask corresponding to the initial parameters from all subtasks as the first subtask to be executed, and execute the first subtask to be executed;
  • the controller uses the filter to filter out the corresponding subtasks from all subtasks according to the current parameter value of the parameter object and executes it until all subtasks of the target execution task are completed.
  • updating the parameter object according to the currently executed subtask includes:
  • the parameter object is read to determine the target subtask being executed when the process is interrupted, including:
  • a filter is used to filter out the subtask corresponding to the target parameter value from all subtasks as the target subtask being executed when the process is interrupted.
  • a corresponding parameter object for saving task execution progress is created for the target execution task, including:
  • the parameter object is read to determine the target subtask being executed when the process is interrupted, including:
  • the task identifier of the target execution task determine the parameter object corresponding to the target execution task from the storage space;
  • the target execution task is divided into a corresponding number of subtasks, including:
  • this application discloses a task management device, including:
  • the segmentation module is used to segment the target execution task to obtain a corresponding number of subtasks, and create a corresponding parameter object for the target execution task to save the task execution progress;
  • the parameter object update module is used to start the task process to execute the subtask and update the parameter object according to the currently executed subtask;
  • the process recovery module is used to read the parameter object to determine the target subtask being executed when the process is interrupted if the task process is interrupted, and re-execute the target subtask to resume the task process.
  • this application discloses an electronic device, including:
  • Memory used to hold computer programs
  • the processor is used to execute the computer program to implement the aforementioned task management method.
  • the present application discloses a computer non-volatile readable storage medium for storing a computer program; wherein the computer program implements the aforementioned task management method when executed by a processor.
  • a corresponding number of subtasks are obtained by dividing the target execution task, and a corresponding parameter object for saving the task execution progress is created for the target execution task; the task process is started to execute the subtasks, and the task process is started according to the currently executed subtasks.
  • the task updates the parameter object; if the task process is interrupted, the parameter object is read to determine the target subtask being executed when the process was interrupted, and the target subtask is re-executed to resume the task process.
  • the target subtask executed at the time of interruption is determined by querying the parameter object, and from The target subtask starts to re-execute the target task, which solves the problem of long-term task interruption running on Kubernetes, enables recovery after long-term task interruption, and reduces repeated actions in the task by dividing the task into multiple subtasks for execution. , saving a lot of time spent on task re-execution and improving task execution efficiency.
  • Figure 1 is a flow chart of a task management method provided by some embodiments of the present application.
  • Figure 2 is a schematic diagram of a specific subtask definition structure provided by some embodiments of the present application.
  • Figure 3 is a specific task execution flow chart provided by some embodiments of the present application.
  • Figure 4 is a specific task recovery flow chart provided by some embodiments of the present application.
  • Figure 5 is a schematic structural diagram of a task management device provided by some embodiments of the present application.
  • Figure 6 is a structural diagram of an electronic device provided by some embodiments of the present application.
  • this application proposes a long-term task management method in the kubernetes scenario, which can improve task execution efficiency.
  • the embodiment of the present application discloses a task management method, as shown in Figure 1.
  • the method may include the following steps:
  • Step S11 Divide the target execution task into a corresponding number of subtasks, and create a corresponding parameter object for saving the task execution progress for the target execution task.
  • the target execution task is first divided to obtain a corresponding number of subtasks, and a corresponding parameter object for saving the task execution progress is created for the target execution task.
  • dividing the target execution task to obtain a corresponding number of subtasks may include: dividing the target execution task according to task idempotence to obtain a corresponding number of idempotent subtasks.
  • An idempotent task means that a task can get the same result no matter whether it is successfully executed once or multiple times. Then this is an idempotent task; therefore, in order to ensure that no matter how many times the task is interrupted, no matter where it is interrupted, ensure that it can get the same result.
  • the correct result is achieved by dividing the target execution task according to task idempotence to ensure the accuracy of the task results generated by re-executing the sub-task after subsequent interruptions.
  • each subtask may also include: defining each subtask according to the task base class and referencing the filter annotation.
  • each subtask corresponds to a parameter value.
  • a parameter value For example, as shown in Figure 2, by providing a task base class and forming a filter through annotations and annotation processors, users can implement the task class by themselves based on the task base class and reference the filter annotation.
  • the task class inherits from the task base class.
  • Each task class Contains at least a set of initial parameters, a series of subtask methods, and each subtask is defined using filter annotations. That is to say, the function method that refers to the filter annotation is considered a subtask.
  • Step S12 Start the task process to execute the subtask, and update the parameter object according to the currently executed subtask.
  • the subtasks of the target execution task are sequentially executed, and the parameter object corresponding to the target execution task is updated at least once each time a subtask is executed.
  • starting a task process to perform a subtask may include: starting the task process through the controller of the task manager and reading initial parameters from the parameter object; using a filter to obtain the initial parameters from the parameter object according to the parameter value corresponding to each subtask. Filter out the subtask corresponding to the initial parameters from all subtasks as the first to-be-executed subtask, and execute the first to-be-executed subtask; when the first to-be-executed subtask is completed, the controller uses the filter according to the parameter object According to the current parameter value, the corresponding subtasks are filtered out from all subtasks and executed until all subtasks of the target execution task are completed.
  • the parameter value corresponding to the subtask is related to the execution process of the target execution task before the task is divided.
  • the parameter object initially stores an initial value, and the subtask corresponding to the initial value is the first subtask of the target execution task.
  • Task by continuously updating the object parameters, the next sub-task to be executed can be determined according to the order of parameter values, until all sub-tasks are completed.
  • updating the parameter object according to the currently executed subtask may include: updating the parameter object according to the parameter value corresponding to the currently executed subtask. It is understandable that the update of the parameter object depends on the implementation of each specific subtask. Generally speaking, in each subtask, there is at least one operation to update the parameter object. By reading the parameter object, it is necessary to be able to accurately determine that the parameter object has been updated. Executed subtasks and unexecuted subtasks; and the parameter object can also be used to save marks during task execution to determine which subtasks have been successfully executed and which need to be re-executed among the executed subtasks. Task.
  • creating a corresponding parameter object for saving the task execution progress for the target execution task may include: creating a corresponding parameter object for the target execution task for saving the task identification (ID), task name, and task entry during the task execution process.
  • the parameter object of the parameter (that is, the updated parameter value of the currently executed subtask), and saves the parameter object to the storage space in a persistent storage manner. That is, the above parameter object is used to save the input parameters required for the task and record the progress of the task. That is, the parameter object can be used to record the task ID, the task class name corresponding to the task, task input parameters, markers during task execution, etc., so that the execution status of the subtask can be judged based on it.
  • parameter objects can be stored in the form of configmap, and the format can be in an easy-to-parse json format; configmap is a resource in the kubernetes platform and is used to record a set of text information, and the text can be any Format.
  • Step S13 If the task process is interrupted, read the parameter object to determine the target subtask being executed when the process was interrupted, and re-execute the target subtask to resume the task process.
  • the parameter object corresponding to the target execution task is read to determine the target subtask being executed when the process was interrupted, and the target subtask is re-executed to resume the task process. Therefore, in some embodiments, tasks that require long-term execution are cut into subtasks one by one, and the target execution task maintains a parameter object correspondingly. During the execution of the subtask, the content in the parameter object is updated as needed. After the task is interrupted, this parameter object can be read to determine the progress of the last execution, and based on this, determine which subtasks need to be executed next. It is suitable for complex tasks with many steps and takes a long time, and has good versatility.
  • reading the parameter object to determine the target subtask being executed when the process is interrupted may include: obtaining the target parameter value currently saved by the parameter object by reading the parameter object; according to the parameter value corresponding to each subtask, using The filter filters out the subtasks corresponding to the target parameter values from all subtasks as the target subtasks being executed when the process is interrupted. It can be understood that the filter uses the parameter value obtained from the parameter object as the triggering condition of the subtask. When the filter is referenced, the parameter value is provided to identify which conditions need to be triggered when the subtask is met. When the filter cannot match When any subtask is executed, the target execution task is considered to have been completed, and the corresponding parameter object can be deleted and the task process can be exited.
  • reading the parameter object to determine the target subtask being executed when the process is interrupted may include: determining the parameter object corresponding to the target execution task from the storage space according to the task identifier of the target execution task; reading A parameter object to determine the target subtask that was executing when the process was interrupted. It can be understood that since there may be multiple task processes in the system at the same time, there are also multiple parameter objects. Therefore, it is necessary to determine the parameter object corresponding to the task after the task is interrupted. In some embodiments, the task identifier is used to distinguish .
  • the business process creates an instance of task class A based on the task base class and references the filter annotation;
  • the business process calls the controller of the task manager and passes task instance A to it;
  • the controller creates task process A and generates a task ID
  • the controller calls k8s-client (the client object that connects to kubernetes and operates its resources), creates the parameter object configmap-A, and writes the initial parameters of the task instance to configmap-A.
  • the matched subtask is action1, and the controller calls and executes action1;
  • the current parameter a 3. Combined with the filter, the controller finds that no subtask matches this condition. The controller considers that task A has been completed and calls k8s-client to delete the parameter object configmap-A.
  • controller When the controller starts, it first calls k8s-client to traverse the parameter object, finds configmap-A, and reads its task ID, corresponding task class name, and parameter value;
  • apiserver is one of the core services of kubernetes and is used to provide a series of http interfaces through which Kubernetes resources can be queried and operated externally; the task manager is responsible for the life cycle management of the task process; The controller in the task manager is responsible for the life cycle management of tasks and is used to create multiple asynchronous task processes on demand.
  • Each task process judges the execution progress of the task based on the parameter values and status values in the corresponding parameter objects, and filters
  • the parameter conditions declared in the controller determine the subtasks that need to be executed next and trigger these subtasks. When no more subtasks can match the parameter values, the task is considered to have ended and the corresponding task process exits. It can be seen from the above that the parameter object is updated in time after the normal execution of action1. After the task is interrupted, there is no need to execute action1 again. The execution starts from action2, that is, the task is restored normally and some repeated actions are avoided.
  • a corresponding number of subtasks are obtained by dividing the target execution task, and a corresponding parameter object for saving the task execution progress is created for the target execution task; the task process is started to execute the subtasks, and Update the parameter object according to the currently executing subtask; if the task process is interrupted, read the parameter object to determine the target subtask being executed when the process was interrupted, and re-execute the target subtask to resume the task process.
  • the target subtask executed at the time of interruption is determined by querying the parameter object, and from The target subtask starts to re-execute the target task, which solves the problem of long-term task interruption running on Kubernetes, enables recovery after long-term task interruption, and reduces repeated actions in the task by dividing the task into multiple subtasks for execution. , saving a lot of time spent on task re-execution and improving task execution efficiency.
  • the embodiment of the present application also discloses a task management device, as shown in Figure 5.
  • the device includes:
  • the segmentation module 11 is used to segment the target execution task to obtain a corresponding number of subtasks, and create a corresponding parameter object for the target execution task for saving the task execution progress;
  • the parameter object update module 12 is used to start the task process to execute the subtask, and update the parameter object according to the currently executed subtask;
  • the process recovery module 13 is used to read the parameter object to determine the target subtask being executed when the process is interrupted if the task process is interrupted, and re-execute the target subtask to resume the task process.
  • a corresponding number of subtasks are obtained by dividing the target execution task, and a corresponding parameter object for saving the task execution progress is created for the target execution task; the task process is started to execute the subtasks, and Update the parameter object according to the currently executing subtask; if the task process is interrupted, read the parameter object to determine the target subtask being executed when the process was interrupted, and re-execute the target subtask to resume the task process.
  • the target subtask executed at the time of interruption is determined by querying the parameter object, and from The target subtask starts to re-execute the target task, which solves the problem of long-term task interruption running on Kubernetes, enables recovery after long-term task interruption, and reduces repeated actions in the task by dividing the task into multiple subtasks for execution. , saving a lot of time spent on task re-execution and improving task execution efficiency.
  • the task management device may include:
  • the subtask definition unit is used to define each subtask based on the task base class and reference the filter annotation. After definition, each subtask corresponds to a parameter value.
  • the parameter object update module 12 may specifically include:
  • the initial parameter reading unit is used to start the task process through the controller of the task manager and read the initial parameters from the parameter object;
  • the first to-be-executed subtask execution unit is used to use filters to filter out the subtasks corresponding to the initial parameters from all subtasks based on the parameter values corresponding to each subtask as the first to-be-executed subtask, and execute the first to-be-executed subtask. Execute subtasks;
  • the remaining subtask execution units are used to use the filter through the controller to filter out the corresponding subtasks from all subtasks according to the current parameter value of the parameter object and execute them until the target is executed. All subtasks of the task are completed.
  • the parameter object update module 12 may specifically include:
  • the parameter object update unit is used to update the parameter object according to the parameter value corresponding to the currently executed subtask;
  • the process recovery module 13 may specifically include:
  • the target parameter value determination unit is used to obtain the target parameter value currently saved by the parameter object by reading the parameter object;
  • the target subtask determination unit is used to use a filter to filter out the subtasks corresponding to the target parameter value from all subtasks according to the parameter value corresponding to each subtask as the target subtask being executed when the process is interrupted.
  • the segmentation module 11 can be used to create a parameter object for the target execution task for saving the task identifier, task name, and task input parameters during the task execution process, and save the parameter object in a persistent storage manner. to storage space.
  • the process recovery module 13 may specifically include:
  • the parameter object determination unit is used to determine the parameter object corresponding to the target execution task from the storage space according to the task identifier of the target execution task;
  • the target subtask determination unit is used to read the parameter object to determine the target subtask being executed when the process is interrupted.
  • the dividing module 11 can be used to divide the target execution task according to the idempotence of the task to obtain a corresponding number of idempotent subtasks.
  • the embodiment of the present application also discloses an electronic device, as shown in FIG. 6 .
  • the content in the figure cannot be considered as any limitation on the scope of the present application.
  • FIG. 6 is a schematic structural diagram of an electronic device 20 provided by an embodiment of the present application.
  • the electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input-output interface 25 and a communication bus 26.
  • the memory 22 is used to store computer programs, and the computer programs are loaded and executed by the processor 21 to implement relevant steps in the task management method disclosed in any of the foregoing embodiments.
  • the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20;
  • the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can Any communication protocol applicable to the technical solution of this application is not specifically limited here;
  • the input and output interface 25 is used to obtain external input data or output data to the external world, and its specific interface type can be selected according to specific application needs. This is not specifically limited.
  • the memory 22, as a carrier for resource storage can be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc.
  • the resources stored thereon include the operating system 221, the computer program 222 and the data 223 including the training set, etc., and the storage
  • the method can be temporary storage or permanent storage.
  • the operating system 221 is used to manage and control each hardware device and computer program 222 on the electronic device 20 to realize the calculation and processing of the massive data 223 in the memory 22 by the processor 21.
  • It can be Windows Server, Netware, Unix, Linux etc.
  • the computer program 222 may further include computer programs that can be used to complete other specific tasks.
  • embodiments of the present application also disclose a computer non-volatile readable storage medium.
  • Computer executable instructions are stored in the computer non-volatile readable storage medium. When the computer executable instructions are loaded and executed by the processor, , implement the task management method steps disclosed in any of the foregoing embodiments.
  • RAM random access memory
  • ROM read-only memory
  • electrically programmable ROM electrically erasable programmable ROM
  • registers hard disks, removable disks, CD-ROMs, or anywhere in the field of technology. any other known form of storage media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)

Abstract

La présente demande se rapporte au domaine de la gestion de tâches. Sont divulgués un procédé et un appareil de surveillance de gestion de tâches, ainsi qu'un dispositif et un support de stockage. Le procédé consiste : à segmenter une tâche d'exécution cible pour obtenir un nombre correspondant de sous-tâches et à créer, pour la tâche d'exécution cible, un objet de paramètre correspondant permettant de stocker une progression d'exécution de tâche ; à démarrer un processus de tâche pour exécuter les sous-tâches, et à mettre à jour l'objet de paramètre selon la sous-tâche actuellement exécutée ; et, si le processus de tâche est interrompu, à lire l'objet de paramètre pour déterminer une sous-tâche cible qui est exécutée lorsque le processus est interrompu, et à ré-exécuter la sous-tâche cible pour récupérer le processus de tâche. De cette manière, le problème de l'interruption d'une tâche de longue durée qui est exécutée sur des Kubernetes est résolu, et la récupération après l'interruption de la tâche de longue durée peut être réalisée ; et, au moyen de la division d'une tâche en une pluralité de sous-tâches à exécuter, des actions répétées dans la tâche sont réduites, et un temps considérable consommé par la ré- exécution de tâche est économisé, ce qui permet d'améliorer l'efficience d'exécution de tâche.
PCT/CN2022/141660 2022-03-31 2022-12-23 Procédé et appareil de gestion de tâches, et dispositif et support de stockage WO2023185137A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210334877.9 2022-03-31
CN202210334877.9A CN114625515A (zh) 2022-03-31 2022-03-31 一种任务管理方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023185137A1 true WO2023185137A1 (fr) 2023-10-05

Family

ID=81905481

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/141660 WO2023185137A1 (fr) 2022-03-31 2022-12-23 Procédé et appareil de gestion de tâches, et dispositif et support de stockage

Country Status (2)

Country Link
CN (1) CN114625515A (fr)
WO (1) WO2023185137A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114625515A (zh) * 2022-03-31 2022-06-14 苏州浪潮智能科技有限公司 一种任务管理方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102388370A (zh) * 2009-06-19 2012-03-21 核心科技有限公司 计算机进程管理
CN109558237A (zh) * 2017-09-27 2019-04-02 北京国双科技有限公司 一种任务状态管理方法及装置
CN113076182A (zh) * 2021-03-24 2021-07-06 成都海光集成电路设计有限公司 计算任务的恢复方法、装置、用户设备及存储介质
CN114625515A (zh) * 2022-03-31 2022-06-14 苏州浪潮智能科技有限公司 一种任务管理方法、装置、设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102388370A (zh) * 2009-06-19 2012-03-21 核心科技有限公司 计算机进程管理
CN109558237A (zh) * 2017-09-27 2019-04-02 北京国双科技有限公司 一种任务状态管理方法及装置
CN113076182A (zh) * 2021-03-24 2021-07-06 成都海光集成电路设计有限公司 计算任务的恢复方法、装置、用户设备及存储介质
CN114625515A (zh) * 2022-03-31 2022-06-14 苏州浪潮智能科技有限公司 一种任务管理方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN114625515A (zh) 2022-06-14

Similar Documents

Publication Publication Date Title
US10453010B2 (en) Computer device, method, and apparatus for scheduling business flow
JP6818014B2 (ja) ジョブ用の動作リトライ方法及び機器
US8140591B2 (en) Enabling workflow awareness within a business process management (BPM) system
CN106575244B (zh) 确保云应用的高可用性的修补过程
JP2016541056A5 (fr)
US20080120618A1 (en) Issuing syncpoints during execution of a batch application to minimize or eliminate periods of record unavailability due to batch related record locking
CN107016016B (zh) 一种数据处理的方法及装置
WO2018000678A1 (fr) Procédé et appareil de planification de traitement de module
US8271768B2 (en) Concurrent handling of exceptions in received aggregate exception structure with supplied exception handlers and marking handled exceptions
WO2020232951A1 (fr) Procédé et dispositif d'exécution de tâche
WO2023185137A1 (fr) Procédé et appareil de gestion de tâches, et dispositif et support de stockage
CN111400011A (zh) 一种实时任务调度方法、系统、设备及可读存储介质
US20150180960A1 (en) Using a same program on a local system and a remote system
US8468386B2 (en) Detecting and recovering from process failures
US10649808B2 (en) Outcome-based job rescheduling in software configuration automation
US20080320275A1 (en) Concurrent exception handling
CN111666141A (zh) 任务调度方法、装置、设备及计算机存储介质
CN107958414B (zh) 一种清除cics系统长交易的方法及系统
CN110109747B (zh) 基于Apache Spark的数据交换方法及系统、服务器
US8239870B2 (en) Scheduling execution of work units with policy based extension of long-term plan
CN112732415B (zh) 基于资源交换代理系统的事务处理方法、装置和设备
JP7024804B2 (ja) システム更新装置およびシステム更新方法
US20230065589A1 (en) Using persistent finite state machine to coordinate lifecycle operations in service broker
CN112272823B (zh) 管理分布式计算系统中的共享资源
CN114064244A (zh) 联机定时交易方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22934952

Country of ref document: EP

Kind code of ref document: A1