CN113867912A - Method and device for executing task, electronic equipment and readable storage medium - Google Patents
Method and device for executing task, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN113867912A CN113867912A CN202111132006.0A CN202111132006A CN113867912A CN 113867912 A CN113867912 A CN 113867912A CN 202111132006 A CN202111132006 A CN 202111132006A CN 113867912 A CN113867912 A CN 113867912A
- Authority
- CN
- China
- Prior art keywords
- task
- execution
- executor
- state
- instruction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 110
- 238000005192 partition Methods 0.000 claims description 28
- 230000002159 abnormal effect Effects 0.000 claims description 24
- 238000001514 detection method Methods 0.000 claims description 21
- 230000000694 effects Effects 0.000 claims description 21
- 230000004044 response Effects 0.000 claims description 20
- 238000000638 solvent extraction Methods 0.000 claims description 4
- 230000004083 survival effect Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000007726 management method Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 239000000284 extract Substances 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000000737 periodic effect Effects 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 238000012790 confirmation Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 239000000306 component Substances 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
Abstract
The application provides a method, a device, an electronic device and a readable storage medium for executing a task, wherein a task request execution instruction sent by a client is received, the task request execution instruction comprises attribute information of the task, and the attribute information comprises an execution mode. And when the execution mode is confirmed to comprise a single-instance mode and the task in the execution state does not exist in the task execution list of the task manager or the execution mode comprises a parallel mode, distributing a corresponding task executor for the task. And sending the execution instruction to a task executor corresponding to the task so as to enable the task executor to execute the task. Therefore, when the execution mode comprises the single-instance mode, if the task in the execution state does not exist in the execution list, the task executor is allocated to the task to execute the task, and when the execution mode comprises the parallel mode, the task executor is directly allocated to the task to execute the task, so that the problems of data coverage, error execution result or task abnormity and the like caused by task overlapping execution are avoided.
Description
Technical Field
The present application relates to the field of information technology, and in particular, to a method and an apparatus for executing a task, an electronic device, and a readable storage medium.
Background
In the current information system, management and scheduling of tasks are important, such as executing periodic planning tasks, executing departing services under given conditions, and the like. In the existing task management and scheduling system, a centralized task scheduling center is generally adopted to uniformly send tasks to be executed to task applications, and the task applications start corresponding task instances to complete the scheduling and execution of sequential tasks.
However, when the same task execution interval is short, especially when a periodic planning task is executed, when the task execution in operation is not finished yet, and the second execution instruction arrives, the task is executed in an overlapping manner, which causes problems such as data coverage, error in execution result, abnormal exit of the task, and the like.
Therefore, a task execution method is needed to solve the above technical problems.
Disclosure of Invention
The application provides a method and a device for executing tasks, electronic equipment and a readable storage medium, which are used for solving the problems of data coverage, error execution result or abnormal exit of the tasks and the like.
In a first aspect, the present application provides a method for executing a task, the method being used for a task manager, comprising:
receiving a task request execution instruction sent by a client, wherein the task request execution instruction comprises attribute information of a task, and the attribute information comprises: an execution mode;
when the execution mode is confirmed to comprise a single-instance mode and the task in the execution state does not exist in a task execution list of the task manager or the execution mode comprises a parallel mode, distributing a corresponding task executor for the task;
and sending an execution instruction to a task executor corresponding to the task so as to enable the task executor to execute the task.
Optionally, the allocating a corresponding task executor to the task specifically includes:
and selecting available task executors from a task executor list, and distributing the available task executors for the tasks.
Optionally, the method further includes:
when the execution mode comprises a single-instance mode and the task in the execution state does not exist in a task execution list of the task manager or the execution mode comprises a parallel mode, allocating a task execution code for the task, marking the execution state of the task as an unallocated state, and recording the attribute information of the task, the task execution code and the execution state of the task in the task execution list;
the selecting available task executors from a task executor list and allocating the available task executors to the tasks specifically comprises:
and selecting available task executors from the task executor list, changing the execution state of the task into a ready state, and distributing the available task executors for the task in the ready state.
Optionally, sending the execution command to the task executor corresponding to the task specifically includes:
generating an execution instruction containing the attribute information, the task execution code and the execution state of the task according to the attribute information, the task execution code and the execution state of the task in the task execution list;
and sending the execution instruction to the task executor corresponding to the task through the IP address of the task executor corresponding to the task.
Optionally, the attribute information includes: the number of partitions;
the method further comprises the following steps:
partitioning the task according to the number of the partitions, and marking each partition;
correspondingly, the allocating a corresponding task executor to the task specifically includes:
and allocating a corresponding task executor to each partition of the task.
Optionally, the method further includes:
sending a survival detection request to a task executor in a task executor list;
if response information of the activity detection request is received, updating the task executor list according to the response information, wherein the response information comprises the execution state of the task executor and the task currently executed by the task executor;
and if the response information is not received after the first preset times of activity detection requests are continuously sent, marking the execution state of the task executor as an offline state.
Optionally, the method further includes:
judging the execution state of the task;
when the execution state comprises an execution state and the task is executed overtime, or the execution state comprises an abnormal state, or the execution state comprises an offline state and the execution mode of the task is a parallel mode, comparing whether the retried times exceed the failed retried times or not;
if yes, deleting the task and the record of the task with the same task execution code as the task from the task execution list, and sending a task exception instruction to all task executors corresponding to the task with the same task execution code as the task; if not, reallocating the task executors for the tasks, and adding one to the retried times.
Optionally, the method further includes:
and when the execution state comprises an offline state and the execution mode of the task is a single-instance mode, marking the execution state of the task with the same task execution code in the task execution list as an abnormal exit state, and sending a task abnormal instruction to the task and all task executors corresponding to the task with the same task execution code.
Optionally, the method further includes:
and when the execution state comprises an end state, inquiring whether the tasks with the same task execution codes as the tasks are all in the end state, if so, sending an end instruction to the tasks and all task executors corresponding to the tasks with the same task execution codes as the tasks, and deleting the tasks and the records of the tasks with the same task execution codes as the tasks from the task execution list.
Optionally, the method further includes:
and if no response information is received after the second preset times of activity detection requests are continuously sent, deleting the records of the task executors in the task executor list, wherein the second preset times is greater than the first preset times.
Optionally, the method further includes:
receiving a registration request of a task executor, wherein the registration request comprises an identifier and an IP address of the task executor, and adding the task executor into a task executor list of the task manager.
In a second aspect, the present application provides a method of performing a task, the method for a task executor, comprising:
receiving an execution instruction sent by a task manager, wherein the execution instruction is generated after the task manager receives a task request execution instruction sent by a client and confirms that an execution mode comprises a single-instance mode and a task in the task request execution instruction in an execution state does not exist in a task execution list of the task manager or the execution mode comprises a parallel mode, and the task request execution instruction comprises attribute information of the task, and the attribute information comprises: an execution mode;
and executing the task according to the execution instruction.
Optionally, the method further includes:
after receiving an execution instruction sent by the task manager, extracting attribute information of a task in the execution instruction, and recording the attribute information in a task execution list in the task executor.
Optionally, the executing the task according to the execution instruction specifically includes:
starting the task according to the execution instruction;
if the starting fails, marking the execution state of the task in the task execution list as abnormal starting;
if the starting is successful, the execution state of the task in the task execution list is marked as being in execution, the state of the task is obtained to judge whether the task is executed and completed, if yes, the execution state is changed into execution completion, and if not, the execution state is changed into execution abnormity.
Optionally, the method further includes:
receiving a control instruction sent by a task manager;
if the control instruction comprises an abnormal instruction or an overtime instruction, executing a failure callback method of the task, and deleting the record of the task in the task execution list;
if the control instruction comprises an end instruction, judging whether the task has a partition;
and if the result is positive, executing the task ending callback method and deleting the records of the tasks in the task execution list, otherwise, deleting the records of the tasks in the task execution list.
In a third aspect, the present application provides an apparatus for performing a task, comprising:
a receiving module, configured to receive a task request execution instruction sent by a client, where the task request execution instruction includes attribute information of a task, and the attribute information includes: an execution mode;
the distribution module is used for distributing corresponding task executors for the tasks when the execution modes comprise a single-instance mode and the tasks in the execution state do not exist in a task execution list of the task manager or the execution modes comprise a parallel mode;
and the sending module is used for sending the execution instruction to the task executor corresponding to the task so as to enable the task executor to execute the task.
In a fourth aspect, the present application provides an apparatus for performing a task, comprising:
a receiving module, configured to receive an execution instruction sent by a task manager, where the execution instruction is generated after the task manager receives a task request execution instruction sent by a client and confirms that an execution mode includes a single-instance mode and a task in the execution instruction in an execution state does not exist in a task execution list of the task manager or the execution mode includes a parallel mode, and the task request execution instruction allocates a corresponding task executor to the task, where the task request execution instruction includes attribute information of the task, and the attribute information includes: an execution mode;
and the execution module is used for executing the task according to the execution instruction.
In a sixth aspect, the present application provides an electronic device, comprising: a memory and a processor;
the memory is used for storing instructions; the processor is used for calling the instructions in the memory to execute the task execution method in any one of the possible designs of the first aspect and the first aspect or any one of the possible designs of the second aspect and the second aspect.
In a seventh aspect, the present application provides a computer-readable storage medium having computer instructions stored thereon, where the computer instructions, when executed by at least one processor of an electronic device, cause the electronic device to perform a method for performing tasks in any one of the possible designs of the first aspect and the first aspect or any one of the possible designs of the second aspect and the second aspect.
In an eighth aspect, the present application provides a computer program product comprising computer instructions that, when executed by at least one processor of an electronic device, cause the electronic device to perform a method for performing tasks in any one of the possible designs of the first aspect and the first aspect or in any one of the possible designs of the second aspect and the second aspect.
The method for executing the task is used for a task manager, the task manager receives a task request execution instruction sent by a client, the task request execution instruction comprises attribute information of the task, and the attribute information comprises an execution mode. And then, when the execution mode is confirmed to comprise a single-instance mode and the task in the execution state does not exist in the task execution list of the task manager or the execution mode comprises a parallel mode, distributing a corresponding task executor for the task. And sending the execution instruction to a task executor corresponding to the task so as to enable the task executor to execute the task. Therefore, when the execution mode comprises the single-instance mode, if the task in the execution state does not exist in the execution list, the task executor is allocated to the task to execute the task, and when the execution mode comprises the parallel mode, the task executor is directly allocated to the task to execute the task, so that the problems of data coverage, error execution result or task abnormity and the like caused by task overlapping execution are avoided.
Drawings
In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic view of a scenario of a method for executing a task according to an embodiment of the present application;
fig. 2 is a signaling interaction diagram of a method for executing a task according to an embodiment of the present application;
fig. 3 is a signaling interaction diagram of a method for performing a task according to an embodiment of the present application;
FIG. 4 is a flowchart of a method for performing tasks according to an embodiment of the present application;
FIG. 5 is a flowchart of a method for performing tasks according to an embodiment of the present application;
FIG. 6 is a flow chart of another method for performing tasks provided by an embodiment of the present application;
FIG. 7 is a flow chart of another method for performing tasks provided by an embodiment of the present application;
FIG. 8 is a schematic diagram of an apparatus for performing tasks according to an embodiment of the present application;
FIG. 9 is a schematic diagram of an apparatus for performing tasks according to an embodiment of the present application;
fig. 10 is a schematic hardware structure diagram of an electronic device according to an embodiment of the present application.
Detailed Description
To make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be clearly and completely described below with reference to the drawings in the present application, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
TASK (TASK) is a running activity of an infinite loop program segment with independent functions, and is the object of scheduling and execution. In the current information system, task management and scheduling play an important role, and the usage scenarios thereof include: and executing a periodical planning task, and triggering an executed service under a customized condition.
The existing task management and scheduling method mostly adopts a centralized task scheduling center to receive an instruction for executing a task and uniformly sends the execution instruction to a task executor, and the task executor executes the task according to an execution command, so that one task is scheduled and executed.
However, when the same task is executed at a short interval, especially when a periodic planning task is executed, if the execution of the running task is not finished yet and the second execution command arrives again, the tasks are executed in an overlapping manner, which causes problems such as data coverage, error in execution result, abnormal exit of the task, and the like.
In order to solve the above problem, the present application provides a method for executing a task, where a task manager receives a task request execution instruction sent by a client, where the task request execution instruction includes attribute information of the task, and the attribute information includes an execution mode. And when the task manager confirms that the execution mode comprises a single-instance mode and no task in an execution state exists in a task execution list of the task manager or the execution mode comprises a parallel mode, allocating a corresponding task executor to the task, and sending an execution instruction to the task executor corresponding to the task to enable the task executor to execute the task. When the execution mode comprises a single-instance mode, if the task in the execution state does not exist in the execution list, the task executor is allocated to the task to execute the task, and when the execution mode comprises a parallel mode, the task executor is directly allocated to the task to execute the task, so that the problems of data coverage, error execution result or task abnormity and the like caused by task overlapping execution are avoided.
The technical solution of the present application will be described in detail below with specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.
Fig. 1 is a schematic view illustrating a scenario of a method for executing a task according to an embodiment of the present application. The client 101 sends a task request execution instruction to the task manager 102, where the task request execution instruction includes attribute information of the task, and the attribute information includes an execution mode. After receiving a task request execution instruction sent by the client 101, the task manager 102 extracts an execution mode in the task request execution instruction, and determines whether a task in the task request execution instruction can be executed according to the execution mode, where the execution mode includes a single-instance mode and when the task in an execution state does not exist in a task execution list of the task manager 102, it is determined that the task in the task request execution instruction can be executed, a task executor 103 is allocated for the task, and the execution instruction is sent to a task executor 103 corresponding to the task. The task executor 103 executes the task when receiving the execution instruction.
Fig. 2 illustrates a signaling interaction diagram of a method for performing a task according to an embodiment of the present application. On the basis of the embodiment shown in fig. 1, as shown in fig. 2, with a task manager as an execution subject, the method of this embodiment may include the following steps:
s101, receiving a task request execution instruction sent by a client, wherein the task request execution instruction comprises attribute information of a task, and the attribute information comprises: the mode is executed.
The TASK manager is also called TASK management scheduling CENTER (TASK _ manager _ CENTER) and is a core component of the system, and is used for receiving TASK execution, partitioning TASKs, selecting TASK executors, issuing instructions, recording execution states and the like in the system. The task partitioning means that one task is divided into a plurality of areas and executed respectively. TASK performers are also known as TASK applications (TASK _ HOST): the application service with the task instance installed and deployed is an entity for actually executing the task, and a plurality of task executors can be deployed in a cluster environment.
The CLIENT (CLIENT) is a trigger condition for deploying the execution plan of the TASK and formulating the TASK, generates a TASK execution REQUEST instruction (TASK _ REQUEST _ CMD), and sends the TASK execution REQUEST instruction (TASK _ REQUEST _ CMD) to the TASK manager. The task manager receives a task request instruction, and the task request instruction comprises attribute information of the task. The attribute information includes: TASK code (TASK _ ID), TASK NAME (TASK _ NAME), execution MODE (RUN _ MODE), number of partitions (sharing _ COUNT), TASK timeout TIME (OVER TIME), number of failed retries (REDO _ TIMEs), execution method (TASK _ handle), failure CALLBACK method (ERROR _ CALLBACK), and TASK end method (FINAL _ CALLBACK). The execution mode comprises a single instance mode (single) and a parallel mode (parallel), wherein the single instance mode refers to that one task in the system only has one running task instance, and the parallel mode refers to that one task in the system can simultaneously have a plurality of task instances to be executed concurrently and a plurality of task instances to be executed concurrently. The number of partitions refers to the number of areas into which the task is divided.
As one implementation, the task request execution instruction may include task code, execution mode, number of partitions, task timeout time, number of failed retries.
S102, when the execution mode is confirmed to comprise a single-instance mode and the task in the execution state does not exist in the task execution list of the task manager or the execution mode comprises a parallel mode, distributing a corresponding task executor for the task.
After receiving a task request execution instruction sent by a client, a task manager extracts an execution mode of a task from the task request execution instruction, and when the execution mode includes a single-instance mode, the task manager queries whether the task in execution exists in a task execution list of the task manager, that is, whether the same task in the task execution list is in execution is queried, if not, the task can be executed is confirmed, and if so, an abnormal message that the single-instance mode does not allow the task to be executed repeatedly is prompted. The TASK execution list is also called a currently executed TASK (TASK _ RUNNING _ record), which is a storage unit for the TASK manager to record the information and status of the TASK currently RUNNING in the system during RUNNING.
When the execution mode includes the parallel mode, it is confirmed that the task can be executed. Therefore, when the confirmation execution mode comprises a single-instance mode and the task in the execution state does not exist in the task execution list or the execution mode comprises a parallel mode, the confirmation task can be executed, and therefore the corresponding task executor is allocated to the task.
As an implementation manner, the method for querying whether the same task is being executed in the task execution list may be to query whether the task in the task execution list has the same task code as the task.
The task manager may query the list of task executors for registered task executors, and sort out available task executors from the list of task executors, such as task executors in an idle state, and then assign the available task executors to the tasks. The task manager can also receive a registration request sent by the task executor, wherein the registration request comprises the identification of the task executor, the IP address and task list information contained in the task executor, and after receiving the registration request, the task executor sending the registration request is added into the task executor list of the task manager.
And S103, sending the execution instruction to a task executor corresponding to the task.
After allocating the corresponding TASK executor to the TASK in the TASK request execution instruction, the TASK manager sends an execution instruction (TASK _ EXECUTE _ CMD) to the corresponding TASK executor. The execution instruction includes TASK execution code (TASK _ running _ ID), TASK code, partition number, and partition index, which can be understood as a label of each partition. In a specific application, the task manager may send the execution instruction to the task executor according to the IP address of the task executor.
And S104, executing the task by the task executor according to the execution instruction.
After receiving an execution instruction sent by the task manager, the task executor establishes a task execution instance, records the task information into a task execution list in the task executor, and then starts the task execution instance. The task execution list in the task executor is a storage unit for the task executor to record the information and the state of the task being executed by the local machine.
According to the task execution method, after the task manager receives the task request execution instruction sent by the client, when the task manager confirms that the execution mode of the task in the task request instruction comprises a single-instance mode and the task in the execution state does not exist in the task execution list or the execution mode comprises a parallel mode, the task manager allocates the task executor to the task to execute the task, and the problems of data coverage, execution result errors or task abnormity and the like caused by task overlapping execution are avoided.
Fig. 3 is a signaling interaction diagram illustrating a method for performing a task according to an embodiment of the present application.
As shown in fig. 3, the method of the present embodiment may include the following steps:
s201, receiving a task request execution instruction sent by a client, wherein the task request execution instruction comprises attribute information of a task, and the attribute information comprises: the mode is executed.
The client sends the task request execution instruction to the task manager, the task manager receives the task request execution instruction sent by the client, and the execution mode of the task is extracted from the task request execution instruction.
S202, when the execution mode is confirmed to comprise a single-instance mode and the task in the execution state does not exist in the task execution list of the task executor or the execution mode comprises a parallel mode, the corresponding task executor and the task execution code are allocated to the task, the execution state of the task is marked as an unallocated state, and the attribute information, the task execution code and the state of the task are recorded in the task execution list.
And when the task manager confirms that the execution mode comprises a single-instance mode, checking whether the task execution list in the task manager has the execution task which is the same as the task in the task request execution instruction, and when the task execution list does not have the execution task which is the same as the task in the task request execution instruction, confirming that the task in the task request execution instruction can be executed. The task manager confirms that the execution mode includes a parallel mode, and also confirms that the task can be executed. The TASK manager confirms that the TASK in the TASK request execution instruction can be executed, allocates a TASK execution code for the TASK, wherein the TASK execution code can be understood as the time for executing the TASK, marks the execution STATE (TASK _ EXECUTE _ STATE) of the TASK as an unallocated STATE (TS _ UNASSIGNED), and records the attribute information of the TASK, the TASK execution code, the STATE of the TASK and other information in a TASK execution list.
As an implementation manner, when the attribute information of the task includes the number of partitions, the task may be partitioned according to the number of partitions, and each partition is marked, where the mark of each partition is a partition INDEX (INDEX) of each partition.
S203, selecting available task executors from the task executor list, changing the execution state of the tasks into a ready state, and distributing the available task executors for the tasks in the ready state.
And the task manager queries available task executors from the task executor list when confirming that the task can be executed. If the available TASK executor is inquired, recording the inquired available TASK executor into a TASK executor IP (TASK _ M _ IP) field in the TASK execution list, and changing the execution state of the TASK in the TASK execution list from an unallocated state to a READY state (TS _ READY). And if the available task executors cannot be inquired, continuously inquiring the task executor list until the available task executors are inquired.
The applicant finds that most tasks executed by a system usually are mainly batch data processing, the execution time of the tasks is long, the processing data amount is large, and if errors occur in the execution process, more data need to be recovered, so that the task manager can divide the tasks according to the number of the partitions by including the number of the partitions in the attribute information of the tasks, the difficulty of dividing the partitions by the tasks is reduced, and task codes are only concentrated in service development. Then, a corresponding task executor can be allocated to each partition, so that one task can be executed by a plurality of task executors, the execution time of the task is reduced, and the probability of execution errors is reduced.
And S204, generating an execution instruction containing the attribute, the task execution code and the execution state of the task according to the attribute information, the task execution code and the execution state of the task in the task execution list.
After distributing available task executors for the tasks in the ready state, the task manager generates execution instructions according to the attribute information, the task execution codes and the execution states of the tasks in the task execution list, wherein the execution instructions comprise the attribute information, the task execution codes and the execution states of the tasks.
And S205, sending the execution instruction to the task executor corresponding to the task through the IP address of the task executor corresponding to the task.
And after generating the execution instruction, the task manager sends the execution instruction to the task executor through the IP address of the task executor corresponding to the task.
And S206, after the task executor receives the execution instruction, executing the task.
And after receiving the execution instruction, the task executor executes the task according to the execution instruction.
According to the task execution method provided by the application, when the task execution mode in the task request instruction is confirmed to comprise a single-instance mode and no task in an execution state exists in a task execution list of the task manager or the execution mode comprises a parallel mode, a task execution code is allocated to the task executor, the execution state of the task is marked as an unallocated state, and attribute information, the task execution code and the execution state of the task are recorded in the task execution list. After the available task executors are acquired, the execution state of the task is changed into a ready state, and the task executors are allocated to the task in the ready state to execute the task. Therefore, the task executors can be accurately distributed to the tasks, and the task execution efficiency is improved.
Fig. 4 is a flowchart illustrating a method for performing a task according to an embodiment of the present application. As shown in fig. 4, the method of this embodiment may include the following steps:
s301, receiving a task request execution instruction sent by a client, wherein the task request execution instruction comprises attribute information of a task, and the attribute information comprises: the mode is executed.
The client generates a task request execution instruction and sends the task request execution instruction to the task manager. And the task manager receives the task request execution instruction and extracts the attribute information of the task in the task request execution instruction.
S302, when the execution mode is confirmed to comprise a single-instance mode and no task in an execution state exists in a task execution list of the task manager or the execution mode comprises a parallel mode, distributing a corresponding task executor for the task.
And when the execution mode comprises a single-instance mode, inquiring whether a task with the same task code as the task exists in a task execution list of the task manager, and if not, confirming that the task in the execution state does not exist in the task execution list, so that the task can be executed. The execution mode includes a parallel mode, confirming that the task is also executable. And after confirming that the task can be executed, allocating a corresponding task executor for the task.
And S303, sending the execution instruction to a task executor corresponding to the task so that the task executor executes the task.
After generating an execution instruction comprising the attribute information, the task execution code and the execution state of the task, the task manager sends the execution instruction to a task executor corresponding to the task, and the task executor executes the task after receiving the execution instruction.
And S304, sending a survival detection request to the task executors in the task executor list in the current period.
The TASK manager periodically sends a sounding request to each TASK executor in the TASK executor list, and judges the STATE (TASK _ HOST _ STATE) of the TASK executor. For example, a liveness request may be sent to a task executor through an IP address of the task executor.
S305, if response information of the activity detection request is received, updating the task execution list according to the response information, and if no response information is received after the activity detection request is continuously sent for the first preset times, marking the execution state of the task executor as an offline state.
The states in which the task executor is normally located include NORMAL (M _ NORMAL), abnormal (M _ ERROR), and OFFLINE (M _ offset). When the task executor is in a normal state, after receiving the activity detection request, the task executor responds to the activity detection request and sends response information to the task manager, and the task manager updates the record information of the task execution list according to the response information. When the task executor is in an abnormal or offline state, the task executor does not respond to the activity detection request after receiving the activity detection request. And if the task manager does not receive the response information after continuously sending the activity detection requests for the first preset times to the task executor, marking the execution state of the task executor as an offline state. And if no response information is received after the second preset times of activity detection requests are continuously sent, deleting the record of the task executor in the task executor list, and deleting the execution task record related to the task executor in the task execution list. The second preset number is greater than the first preset number, for example, the second preset number is twice the first preset number.
In this embodiment, the steps S301 and S304 are not limited by the described operation sequence, and the steps S301 and S304 may be performed in other sequences or simultaneously.
According to the method for executing the task, the task manager periodically sends the activity detection request to each task executor in the task executor list, and timely acquires the current state of each task executor, so that the task is prevented from being distributed to the task executor in an abnormal or offline state during task distribution, and the task execution efficiency is improved.
Fig. 5 is a flowchart illustrating a method for performing a task according to an embodiment of the present application. As shown in fig. 5, the method of this embodiment may include the following steps:
s401, receiving a task request execution instruction sent by a client, wherein the task request execution instruction comprises attribute information of a task, and the attribute information comprises: the mode is executed.
S402, when the execution mode is confirmed to comprise a single-instance mode and no task in an execution state exists in a task execution list of the task manager or the execution mode comprises a parallel mode, distributing a corresponding task executor for the task.
And S403, sending the execution instruction to a task executor corresponding to the task so that the task executor executes the task.
And S404, sending a survival detection request to the task executors in the task executor list.
S405, if response information of the activity detection request is received, updating the task execution list according to the response information, and if no response information is received after the activity detection request is continuously sent for the first preset times, marking the execution state of the task executor as an offline state.
Step S401 is similar to step S301, step S402 is similar to step S302, step S403 is similar to step S303, step S404 is similar to step S304, and step S405 is similar to step S305, which are not described herein again.
And S406, judging the execution state of the task.
The execution state of the task may include in-execution (TS _ RUNNING), timeout (TS _ OVERTIME), END (TS _ END), exception (TS _ ERROR), exception EXIT (TS _ ERROR _ EXIT), and OFFLINE (TS _ OFFLINE). If the execution state includes the state in execution, determining whether the task being executed is OVERTIME when the task executor is in the state in execution, if so, executing step S407 and generating a task timeout instruction (CMD _ override) to the corresponding task executor, if the execution state includes the abnormal state, executing step S407 and sending a task abnormal instruction (CMD _ ERROR) to the task executor corresponding to the task, if the execution state includes the state in offline, determining an execution mode of the task, and if the execution mode includes the parallel mode, executing step S407. If the execution status includes an offline status and the execution mode of the task includes a single instance mode, step S408 is performed. If the execution status includes the end status, step S409 is executed.
S407, comparing whether the retried times exceed the failed retried times.
It is determined whether the number of times the task is re-executed exceeds the number of failed retries in the task attribute. If yes, go to step S410, otherwise go to step S411.
S408, marking the execution state of the task with the same task execution code in the task execution list as an abnormal exit state, and sending a task abnormal instruction to the task and all task executors corresponding to the task with the same task execution code.
When the execution mode of the task comprises a single-instance mode, marking the execution state of the task which has the same task execution code as the task in the task request execution instruction in the task execution list as an abnormal exit state, and sending a task abnormal instruction to the task executor of the task and all task executors corresponding to the tasks which have the same task execution code as the task.
And S409, inquiring whether the tasks with the same task execution codes as the task are all in an end state, if so, sending an end instruction to the task and all task executors corresponding to the tasks with the same execution codes as the task, and deleting the record of the task and the tasks with the same task execution codes as the task from the task execution list.
When the execution state of the task is in an end state, whether the tasks with the same task execution codes as the tasks in the task request execution instruction are all in the end state is inquired, if yes, the task executer corresponding to the task and all the task executers corresponding to the tasks with the same task execution codes send an end instruction, and records of the task and the tasks with the same task execution codes as the task are deleted from a task execution list.
And S410, deleting the task and the record of the task with the same task execution code from the task execution list, and sending a task exception instruction to all task executors corresponding to the task with the same task execution code.
S411, the task executor is redistributed to the task, and the number of retried times of the task is increased by one.
When the number of retries of the task does not exceed the number of failed retries, the task is re-executed, and the method of re-executing the task may be to re-assign a task executor to the task while adding one to the number of retries of the task. The task may be re-marked as an unallocated state, then the available task executors are selected from the task executor list, the state of the task is changed from the unallocated state to a ready state, and then the task in the ready state is changed to allocate the available task executors.
It will be appreciated that the task referred to above is a task in the task request execution instruction.
According to the method for executing the task, the state of the task is monitored in real time in the task executing process, corresponding processing is carried out according to the state of the task, timeliness and flexibility are high, and the task executing efficiency is improved.
In the above detailed description of the method for executing a task provided in the embodiments of the present application, another method for executing a task is also provided in the embodiments of the present application, and with reference to fig. 6, the method is applied to a task executor, and includes:
s501, receiving an execution instruction sent by the task manager.
And the task executor receives an execution instruction sent by the task manager. The execution instruction is generated after distributing a corresponding task executor for the task when the task manager receives the task request execution instruction of the client and confirms that the execution mode comprises a single-instance mode and the task in the task request execution instruction in the execution state is not included in a task execution list in the task manager or the execution mode comprises a parallel mode, wherein the task request execution instruction comprises attribute information of the task, and the attribute information comprises the execution mode.
The task executor may extract attribute information of the task in the task execution instruction after receiving the execution instruction sent by the task manager, and record the attribute information in a task execution list in the task executor. Each task executor has a task execution list, and the task execution list in the task executor is a storage unit for recording the information and the state of the task being executed by the local machine.
And S502, executing the task according to the execution instruction.
After receiving the execution instruction, the task executor starts a task in the execution instruction, if the start fails, marks a task execution state in a task execution list in the task executor as start exception, if the start succeeds, marks the task execution state in the task execution list in the task executor as in execution, monitors the state of the task in real time to judge whether the task is executed and completed, if the execution is completed, changes the execution state from execution to execution completion, and if the execution is not completed, changes the execution state from execution to execution exception.
According to the method for executing the tasks, the execution instruction sent by the task manager is received, the execution mode of the tasks in the execution instruction comprises a single-instance mode, the execution mode of the tasks or the execution mode of the tasks which are not in the execution state in the task execution list comprises a parallel mode, and the problems of data coverage, execution result errors or task abnormity and the like caused by task overlapping execution can be avoided in the process of executing the tasks.
Fig. 7 is a flowchart illustrating another method for performing a task according to an embodiment of the present application. As shown in fig. 7, the method of this embodiment may include the following steps:
s601, receiving an execution instruction sent by the task manager.
After receiving a task request execution instruction sent by a client, the task manager generates an execution instruction according to the task request execution instruction and sends the execution instruction to the task executor. And the task executor receives an execution instruction sent by the task manager.
And S602, executing the task according to the execution instruction.
And the task executor executes the task according to the execution instruction after receiving the execution instruction.
And S603, receiving a control command sent by the task manager.
If the control command includes an exception command or a timeout command, the process proceeds to step S604. If the control command includes an end command, the process proceeds to step S605.
S604, executing the failure callback method of the task, and deleting the record of the task in the task execution list.
When the task manager sends an abnormal instruction or a timeout instruction, a failure callback method of the task is executed, and the failure callback method includes: it is determined whether the number of times the task is re-executed exceeds the number of failed retries in the task attribute. If yes, deleting the record of the task with the same task execution code as the task from the task execution list, and sending a task exception instruction to all task executors corresponding to the task with the same task execution code as the task. If not, the task executor is redistributed for the task, and the number of retried times of the task is increased by one.
And S605, judging whether the task has a partition.
If so, the process proceeds to step S606, otherwise, the process proceeds to step S607. When the task has the partition, executing the ending callback method of the task. If not, directly deleting the record of the task in the task execution list, and also deleting the record of the task having the same task execution code with the task.
And S606, executing the ending callback method of the task and deleting the record of the task in the task execution list.
The end callback method includes, for example: and inquiring whether the tasks with the same task execution codes as the task are all in an end state, if so, sending an end instruction to the task executer of the task and all the task executers corresponding to the tasks with the same task execution codes as the task, and deleting the record of the tasks with the same task execution codes as the task from the task execution list.
And S607, deleting the record of the task in the task execution list.
According to the method for executing the task, the control instruction sent by the task manager is received, corresponding processing is carried out according to the control instruction, timeliness and flexibility are high, and task execution efficiency is improved.
Fig. 8 is a schematic structural diagram of an apparatus for performing tasks according to an embodiment of the present application, and as shown in fig. 8, an apparatus 10 for performing tasks according to the present embodiment includes:
a receiving module 11, configured to receive a task request execution instruction sent by a client, where the task request execution instruction includes attribute information of a task, and the attribute information includes: an execution mode;
the allocation module 12 is configured to allocate a corresponding task executor to a task when it is determined that the execution mode includes a single-instance mode and no task in an execution state exists in a task execution list of the task manager or the execution mode includes a parallel mode;
and the sending module 13 is configured to send the execution instruction to a task executor corresponding to the task, so that the task executor executes the task.
The apparatus 10 for performing a task according to the embodiment of the present application may perform the first method embodiment, and for details of implementation principles and technical effects, reference may be made to the method embodiment, which is not described herein again.
Fig. 9 is a schematic structural diagram of an apparatus for performing tasks according to an embodiment of the present invention, and as shown in fig. 9, an apparatus 20 for performing tasks according to the present embodiment includes:
the receiving module 21 is configured to receive an execution instruction sent by a task manager, where the execution instruction is generated after the task manager receives a task request execution instruction sent by a client and confirms that an execution mode includes a single-instance mode and a task in the execution instruction in an execution state does not exist in a task execution list of the task manager or the execution mode includes a parallel mode, and the task request execution instruction task is generated after a corresponding task executor is allocated to the task, where the attribute information includes: an execution mode;
and the execution module 22 is used for executing the task according to the execution instruction.
The apparatus 20 for performing a task provided in the embodiment of the present application may perform the second method embodiment, and for details of implementation principles and technical effects, reference may be made to the method embodiment described above, which is not described herein again.
Fig. 10 shows a hardware structure diagram of an electronic device according to an embodiment of the present application. As shown in fig. 10, the electronic device 30 is configured to implement the operations corresponding to the electronic device in any of the method embodiments described above, where the electronic device 30 of this embodiment may include: memory 31, processor 32 and communication interface 33.
A memory 31 for storing computer instructions. The Memory 31 may include a Random Access Memory (RAM), a Non-Volatile Memory (NVM), at least one disk Memory, a usb disk, a removable hard disk, a read-only Memory, a magnetic disk or an optical disk.
And a processor 32 for executing the computer instructions stored in the memory to implement the information pushing method in the above embodiments. Reference may be made in particular to the description relating to the method embodiments described above. The Processor 32 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor, or in a combination of the hardware and software modules within the processor.
Alternatively, the memory 31 may be separate or integrated with the processor 32.
The electronic device 30 may also include a bus when the memory 31 is a separate device from the processor 32. The bus is used to connect the memory 31 and the processor 32. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, the buses in the figures of the present application are not limited to only one bus or one type of bus.
The communication interface 33 may be connected to the processor 31 via a bus. The processor 32 may control the communication interface 33 to implement the functions of data transmission and reception.
The electronic device provided in this embodiment can be used to execute the task execution method, and its implementation manner and technical effect are similar, which are not described herein again.
The present application also provides a computer readable storage medium, in which computer instructions are stored, and the computer instructions are executed by a processor to implement the methods provided by the above-mentioned various embodiments.
The present application also provides a computer program product comprising computer instructions stored in a computer readable storage medium. The computer instructions may be read by at least one processor of the device from a computer-readable storage medium, and execution of the computer instructions by the at least one processor causes the device to perform the methods provided by the various embodiments described above.
The embodiment of the present application further provides a chip, which includes a memory and a processor, where the memory is used to store computer instructions, and the processor is used to call and execute the computer instructions from the memory, so that a device in which the chip is installed executes the method described in the above various possible embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same. Although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: it is also possible to modify the solutions described in the previous embodiments or to substitute some or all of them with equivalents. And the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (19)
1. A method for performing a task, the method for a task manager, comprising:
receiving a task request execution instruction sent by a client, wherein the task request execution instruction comprises attribute information of a task, and the attribute information comprises: an execution mode;
when the execution mode is confirmed to comprise a single-instance mode and the task in the execution state does not exist in a task execution list of the task manager or the execution mode comprises a parallel mode, distributing a corresponding task executor for the task;
and sending an execution instruction to a task executor corresponding to the task so as to enable the task executor to execute the task.
2. The method according to claim 1, wherein the allocating corresponding task executors to the tasks specifically includes:
and selecting available task executors from a task executor list, and distributing the available task executors for the tasks.
3. The method of claim 2, further comprising:
when the execution mode comprises a single-instance mode and the task in the execution state does not exist in a task execution list of the task manager or the execution mode comprises a parallel mode, allocating a task execution code for the task, marking the execution state of the task as an unallocated state, and recording the attribute information of the task, the task execution code and the execution state of the task in the task execution list;
the selecting available task executors from a task executor list and allocating the available task executors to the tasks specifically comprises:
and selecting available task executors from the task executor list, changing the execution state of the task into a ready state, and distributing the available task executors for the task in the ready state.
4. The method according to claim 3, wherein sending the execution command to the task executor corresponding to the task specifically includes:
generating an execution instruction containing the attribute information, the task execution code and the execution state of the task according to the attribute information, the task execution code and the execution state of the task in the task execution list;
and sending the execution instruction to the task executor corresponding to the task through the IP address of the task executor corresponding to the task.
5. The method of claim 1, wherein the attribute information comprises: the number of partitions;
the method further comprises the following steps:
partitioning the task according to the number of the partitions, and marking each partition;
correspondingly, the allocating a corresponding task executor to the task specifically includes:
and allocating a corresponding task executor to each partition of the task.
6. The method of claim 3, further comprising:
sending a survival detection request to a task executor in a task executor list;
if response information of the activity detection request is received, updating the task executor list according to the response information, wherein the response information comprises the execution state of the task executor and the task currently executed by the task executor;
and if the response information is not received after the first preset times of activity detection requests are continuously sent, marking the execution state of the task executor as an offline state.
7. The method of claim 6, further comprising:
judging the execution state of the task;
when the execution state comprises an execution state and the task is executed overtime, or the execution state comprises an abnormal state, or the execution state comprises an offline state and the execution mode of the task is a parallel mode, comparing whether the retried times exceed the failed retried times or not;
if yes, deleting the task and the record of the task with the same task execution code as the task from the task execution list, and sending a task exception instruction to all task executors corresponding to the task with the same task execution code as the task; if not, reallocating the task executors for the tasks, and adding one to the retried times.
8. The method of claim 7, further comprising:
and when the execution state comprises an offline state and the execution mode of the task is a single-instance mode, marking the execution state of the task with the same task execution code in the task execution list as an abnormal exit state, and sending a task abnormal instruction to the task and all task executors corresponding to the task with the same task execution code.
9. The method of claim 7, further comprising:
and when the execution state comprises an end state, inquiring whether the tasks with the same task execution codes as the tasks are all in the end state, if so, sending an end instruction to the tasks and all task executors corresponding to the tasks with the same task execution codes as the tasks, and deleting the tasks and the records of the tasks with the same task execution codes as the tasks from the task execution list.
10. The method of claim 6, further comprising:
and if no response information is received after the second preset times of activity detection requests are continuously sent, deleting the records of the task executors in the task executor list, wherein the second preset times is greater than the first preset times.
11. The method of claim 1, further comprising:
receiving a registration request of a task executor, wherein the registration request comprises an identifier and an IP address of the task executor, and adding the task executor into a task executor list of the task manager.
12. A method of performing a task, the method being for a task executor, comprising:
receiving an execution instruction sent by a task manager, wherein the execution instruction is generated after the task manager receives a task request execution instruction sent by a client and confirms that an execution mode comprises a single-instance mode and a task in the task request execution instruction in an execution state does not exist in a task execution list of the task manager or the execution mode comprises a parallel mode, and the task request execution instruction comprises attribute information of the task, and the attribute information comprises: an execution mode;
and executing the task according to the execution instruction.
13. The method of claim 12, further comprising:
after receiving an execution instruction sent by the task manager, extracting attribute information of a task in the execution instruction, and recording the attribute information in a task execution list in the task executor.
14. The method according to claim 12, wherein the executing the task according to the execution instruction specifically includes:
starting the task according to the execution instruction;
if the starting fails, marking the execution state of the task in the task execution list as abnormal starting;
if the starting is successful, the execution state of the task in the task execution list is marked as being in execution, the state of the task is obtained to judge whether the task is executed and completed, if yes, the execution state is changed into execution completion, and if not, the execution state is changed into execution abnormity.
15. The method of claim 12, further comprising:
receiving a control instruction sent by a task manager;
if the control instruction comprises an abnormal instruction or an overtime instruction, executing a failure callback method of the task, and deleting the record of the task in the task execution list;
if the control instruction comprises an end instruction, judging whether the task has a partition;
and if the result is positive, executing the task ending callback method and deleting the records of the tasks in the task execution list, otherwise, deleting the records of the tasks in the task execution list.
16. An apparatus for performing a task, the apparatus comprising:
a receiving module, configured to receive a task request execution instruction sent by a client, where the task request execution instruction includes attribute information of a task, and the attribute information includes: an execution mode;
the distribution module is used for distributing corresponding task executors for the tasks when the execution modes comprise a single-instance mode and the tasks in the execution state do not exist in a task execution list of the task manager or the execution modes comprise a parallel mode;
and the sending module is used for sending the execution instruction to the task executor corresponding to the task so as to enable the task executor to execute the task.
17. An apparatus for performing a task, the apparatus comprising:
a receiving module, configured to receive an execution instruction sent by a task manager, where the execution instruction is generated after the task manager receives a task request execution instruction sent by a client and confirms that an execution mode includes a single-instance mode and a task in the execution instruction in an execution state does not exist in a task execution list of the task manager or the execution mode includes a parallel mode, and the task request execution instruction allocates a corresponding task executor to the task, where the task request execution instruction includes attribute information of the task, and the attribute information includes: an execution mode;
and the execution module is used for executing the task according to the execution instruction.
18. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to implement a method of performing a task as claimed in any one of claims 1 to 11 or a method of performing a task as claimed in any one of claims 12 to 15.
19. A computer-readable storage medium, having stored thereon computer instructions for, when executed by a processor, implementing a method of performing a task as claimed in any one of claims 1 to 11 or a method of performing a task as claimed in any one of claims 12 to 15.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111132006.0A CN113867912A (en) | 2021-09-26 | 2021-09-26 | Method and device for executing task, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111132006.0A CN113867912A (en) | 2021-09-26 | 2021-09-26 | Method and device for executing task, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113867912A true CN113867912A (en) | 2021-12-31 |
Family
ID=78990897
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111132006.0A Pending CN113867912A (en) | 2021-09-26 | 2021-09-26 | Method and device for executing task, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113867912A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2707680A1 (en) * | 2006-03-14 | 2007-09-20 | Transgaming Inc. | General purpose software parallel task engine |
| US7975001B1 (en) * | 2007-02-14 | 2011-07-05 | The Mathworks, Inc. | Bi-directional communication in a parallel processing environment |
| CN108804240A (en) * | 2018-04-25 | 2018-11-13 | 天津卓易云科技有限公司 | A kind of distribution of queuing data and Processing Algorithm |
| CN110572433A (en) * | 2019-08-05 | 2019-12-13 | 视联动力信息技术股份有限公司 | Video scheduling method, system and device |
| CN110727509A (en) * | 2019-09-24 | 2020-01-24 | 浙江大搜车软件技术有限公司 | Task scheduling method and device, computer equipment and storage medium |
| CN111241177A (en) * | 2019-12-31 | 2020-06-05 | 中国联合网络通信集团有限公司 | Data acquisition method, system and network equipment |
| CN111274052A (en) * | 2020-01-19 | 2020-06-12 | 中国平安人寿保险股份有限公司 | Data distribution method, server, and computer-readable storage medium |
| CN111522649A (en) * | 2019-02-01 | 2020-08-11 | 北京京东尚科信息技术有限公司 | Distributed task allocation method, device and system |
| CN111666191A (en) * | 2020-06-09 | 2020-09-15 | 贝壳技术有限公司 | Data quality monitoring method and device, electronic equipment and storage medium |
-
2021
- 2021-09-26 CN CN202111132006.0A patent/CN113867912A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2707680A1 (en) * | 2006-03-14 | 2007-09-20 | Transgaming Inc. | General purpose software parallel task engine |
| US7975001B1 (en) * | 2007-02-14 | 2011-07-05 | The Mathworks, Inc. | Bi-directional communication in a parallel processing environment |
| CN108804240A (en) * | 2018-04-25 | 2018-11-13 | 天津卓易云科技有限公司 | A kind of distribution of queuing data and Processing Algorithm |
| CN111522649A (en) * | 2019-02-01 | 2020-08-11 | 北京京东尚科信息技术有限公司 | Distributed task allocation method, device and system |
| CN110572433A (en) * | 2019-08-05 | 2019-12-13 | 视联动力信息技术股份有限公司 | Video scheduling method, system and device |
| CN110727509A (en) * | 2019-09-24 | 2020-01-24 | 浙江大搜车软件技术有限公司 | Task scheduling method and device, computer equipment and storage medium |
| CN111241177A (en) * | 2019-12-31 | 2020-06-05 | 中国联合网络通信集团有限公司 | Data acquisition method, system and network equipment |
| CN111274052A (en) * | 2020-01-19 | 2020-06-12 | 中国平安人寿保险股份有限公司 | Data distribution method, server, and computer-readable storage medium |
| CN111666191A (en) * | 2020-06-09 | 2020-09-15 | 贝壳技术有限公司 | Data quality monitoring method and device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 张西林等: "多重不确定因素影响下的高端装备研制任务流程优化", 《系统工程理论与实践》, vol. 39, no. 3, 25 March 2019 (2019-03-25), pages 725 - 734 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109814998A (en) | A kind of method and device of multi-process task schedule | |
| CN110311831B (en) | Container cloud-based system resource monitoring method and related equipment | |
| CN107168777B (en) | Method and device for scheduling resources in distributed system | |
| CN111190810B (en) | Method, device, server and storage medium for executing test task | |
| CN112527489A (en) | Task scheduling method, device and equipment and computer readable storage medium | |
| CN114884838A (en) | Monitoring method of Kubernetes component and server | |
| CN114168302A (en) | Task scheduling method, device, equipment and storage medium | |
| CN102165426B (en) | Memory management techniques selectively using mitigations to reduce errors | |
| CN107122271B (en) | Method, device and system for recovering node event | |
| CN105874426A (en) | Batch processing method and device for system invocation commands | |
| CN110795234A (en) | Resource scheduling method and device | |
| EP4006725A1 (en) | Virtual machine migration processing and strategy generation method, apparatus and device, and storage medium | |
| CN111831408A (en) | Asynchronous task processing method and device, electronic equipment and medium | |
| CN111709723A (en) | RPA business process intelligent processing method, device, computer equipment and storage medium | |
| CN113867912A (en) | Method and device for executing task, electronic equipment and readable storage medium | |
| CN112130904B (en) | Processing system, inter-processor communication method, and shared resource management method | |
| CN110390450B (en) | Storage scheduling method and device, storage medium and electronic equipment | |
| CN113342499B (en) | Distributed task calling method, device, equipment, storage medium and program product | |
| CN111352710B (en) | Process management method and device, computing equipment and storage medium | |
| CN114020420A (en) | Distributed to-be-executed task execution method and system, storage medium and terminal | |
| CN112596915A (en) | Distributed lock scheduling method, device, equipment and medium | |
| CN113886043B (en) | Simulation task scheduling system for comprehensively deploying public cloud and private cloud | |
| CN113703930A (en) | Task scheduling method, device and system and computer readable storage medium | |
| CN108073453B (en) | Method and device for scheduling CPU (Central processing Unit) resources in distributed cluster | |
| CN115103020B (en) | Data migration processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |