CN111143044A - Task scheduling management system, method, device and storage medium thereof - Google Patents
Task scheduling management system, method, device and storage medium thereof Download PDFInfo
- Publication number
- CN111143044A CN111143044A CN201911260131.2A CN201911260131A CN111143044A CN 111143044 A CN111143044 A CN 111143044A CN 201911260131 A CN201911260131 A CN 201911260131A CN 111143044 A CN111143044 A CN 111143044A
- Authority
- CN
- China
- Prior art keywords
- task
- unit
- management
- instance
- management center
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
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/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application discloses a task scheduling management system, method, device and storage medium thereof, compared with the prior art: configuring task parameters and task scheduling on a visual interface; standardizing a standard task interface, providing a platform-level task scheduling center, and improving the development efficiency of engineers; the task execution log is recorded, so that the log can be conveniently tracked by related responsible persons, an early warning threshold value is provided, different early warning mechanisms are dynamically configured, and the method is flexible and universal; the cluster deploys a task executor to ensure high availability of tasks; the disaster recovery mechanism is independently researched and developed, the state of a task executor is monitored through a heartbeat packet, a platform automatically processes a disaster recovery server, faults are transferred, and the usability of a program is improved; the method has the advantages that a gray scale upgrading mechanism is realized, the concept of version numbers is provided, developers can smoothly upgrade the task version, dynamic routing strategies are configured on the bottom layer through Socket communication, the purpose of smooth upgrading is achieved, and the situations of task execution loss and the like caused by upgrading are avoided.
Description
Technical Field
The present application relates to the field of task management technologies, and in particular, to a task scheduling management system, method, apparatus, and storage medium thereof.
Background
Currently, a traditional task scheduling framework, such as the quartz framework, can solve the task log management problem, being responsible for executing (or notifying) the system of other software components when a predetermined (calendared) time arrives. quartz can be instantiated as a cluster of independent items (with load balancing and fault tolerance capabilities). The quartz can be executed by cron expression accurate to a specific time, each time a new task class object is created.
Disclosure of Invention
In order to solve the foregoing technical problems, embodiments of the present application provide a task scheduling management system, method, apparatus, and storage medium thereof.
A first aspect of an embodiment of the present application provides a task scheduling management system, which may include:
the management center unit is used as an operation interface and used for issuing scheduling operation and command issuing operation of all tasks;
the execution unit is composed of individually operable components and used for receiving the command of the management center unit and sending the command to the task instance unit;
the task instance unit is composed of independent executable components and comprises a plurality of task sub-units, and each task sub-unit is a minimum executable unit and represents different task contents;
and a communication channel is arranged between the execution unit and the task force unit, and the execution unit is used for managing the operation of the task instance unit.
Furthermore, the management center unit is specifically used as a web end management interface of the task scheduling management system, the state information of the currently managed task instance unit and the currently managed execution unit can be clearly checked, an external standard restful interface is arranged, and the external standard restful interface is called by the execution unit and the task instance unit.
Further, the management center unit judges whether all task nodes under the current execution unit are normal or not through heartbeat packet monitoring, judges that the current service is unavailable under the condition that the target node does not respond in the configuration rule, completely migrates all task nodes under the execution unit to a server corresponding to another available execution unit through a fault transfer mechanism, and starts all current backup task nodes.
Furthermore, the execution unit adopts a dynamic routing strategy to achieve connection management of different task instance versions, when the management center unit specifies a new version, the execution unit monitors that the new version is available, and then the task executes and calls Socket connection of the new version to communicate, so as to achieve the purpose of calling a new task, complete excessive gray scale upgrade without restarting, and after the dynamic routing strategy finds the new connection, the execution unit automatically closes the old version task instance.
Further, the task sub-unit comprises
And the task processor object instance is used for scheduling by the execution unit, and after the task instance is started, the task information is automatically registered for unified management of the management center unit.
Furthermore, an RPC communication unit is arranged between the execution unit and the task instance unit, and an RPC communication protocol is contained in the RPC communication unit and used for maintaining a communication mechanism between the execution unit and the task instance unit. The method comprises the following steps:
a second aspect of the present application provides a task scheduling management method, including:
acquiring a developed task instance SpringA jar package of Boot is uploaded through a management center;
the management center checks the actuator resource, issues a command to call an actuator interface, and informs the actuator to start asynchronous downloading of a task instance jar packet;
after the Task instance is started, a plurality of tasks in the Task instance are automatically registered through a Restful interface of a management center, the management center dynamically configures the scheduling time of the Task instance through the interface, and the remote management of the Task instance is realized by issuing start, stop, deletion and update commands through commands;
after the Task instance completes Task execution, reporting the complete execution log through a Restful interface provided by a management centerIn
For in management of
Boundary of China
Checking; when the asynchronous execution log callback fails due to the exception of the management center, the serialized log information of the machine is processed by an actuator asynchronous daemon thread.
Furthermore, the management center issues a command by calling a restful interface of the executor, the executor end local machine maintains an MQ downloading queue thread pool, and when the management center downloading command is received, an asynchronous downloading thread is started to download a remote task instance jar file;
after the executor completes asynchronous downloading, it sends an Advice notification to manage
Has been downloaded and managed
Matching information, recording the corresponding information
And the library is used for the interface end to check and manage.
In a third aspect, an embodiment of the present application provides a management device, which includes a memory and a processor, where the memory stores computer-executable instructions, and the processor implements the system of the first aspect when executing the computer-executable instructions on the memory.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the system of the first aspect is implemented.
In the embodiment of the application, by means of task centralization and visualization configuration, an operable web management interface is provided, tasks are managed automatically, a standardized task interface is provided, and the development is rapid, simple, light and easy to expand.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a logic diagram of a management system provided by an embodiment of the present application;
FIG. 2 is an interface diagram of a management system provided by an embodiment of the present application;
fig. 3 is a schematic structural diagram of a management device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of 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.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In the prior art, tasks cannot be visualized and are inconvenient to manage. The time rule is inconvenient to change, and the database time rule is required to be changed synchronously. When all nodes run on the same server, all nodes will terminate when the server crashes, and the timed task will not execute normally. When the nodes are not on the same server, the nodes affect the states of other nodes due to possible desynchronization of clocks.
Therefore, the task scheduling management system proposed by the present application includes a management center unit 310, an execution unit 320, and a task instance unit 330.
The management center unit 310 is used as an operation interface to issue scheduling operations and command issuing operations of all tasks, and is specifically used as a web-side management interface of the task scheduling management system, so that the state information of the currently managed task instance unit and the currently managed execution unit can be clearly checked, an external standard restful interface is provided, and the external standard restful interface is called by the execution unit and the task instance unit.
The management center unit 310 judges whether all task nodes under the current executor are normal or not through heartbeat packet monitoring, judges that the current service is unavailable when the target node does not respond in the configuration rule, and at this time, all task nodes under the executor are completely migrated to the other available executor servers through a fault transfer mechanism, and all current backup task nodes are started, so that the whole process platform automatically completes the operations of migrating, starting the task nodes and the like, and the normal operation of the execution condition of the task is ensured.
The management center unit 310 provides a version mechanism of the task instance, different version instances of the task instance are automatically started through an actuator dynamic routing strategy, the task execution is communicated with the task instance through a Socket, the actuator end adopts the dynamic routing strategy to achieve connection management of different task instance versions, when the center end designates the new version, the actuator monitors that the new version is available, at the moment, the task execution calls the Socket connection of the new version to communicate, the purpose of calling a new task is achieved, the gray scale upgrading is over-completed under the condition that the whole process is not restarted, after the dynamic routing strategy finds the new connection, the actuator automatically closes the old version task instance, server resources are saved, and the whole gray scale upgrading process is completed.
The execution unit 320 is composed of individually executable components, and is configured to receive a command from the management center unit and issue the command to the task instance unit.
Handle
The manager is a bridge between the management center and the task instance, and executes the task instance when the management center issues the executor through a command
The devices facilitate completion by communicating with the RPC within the task instance
And (4) managing the complete remote call. Executor and task instance
Is as follows
Can be transported separately
The Springboot-jar component and the execution method thereof
The device and task instance are deployed in the same way by default
On the desk server
Deployment and operation of the device need to be implemented in advance by a developer,
the deployment and operation of the task instance are performed through execution
The machine is used for automatically managing operation and maintenance.
The execution unit adopts a dynamic routing strategy to achieve connection management of different task instance versions, when the management center unit designates a new version, the execution unit monitors that the new version is available, the task executes and calls Socket connection of the new version for communication, the purpose of calling a new task is achieved, excessive gray scale upgrading is completed under the condition of no restarting, and after the dynamic routing strategy finds the new connection, the execution unit automatically closes an old version task instance.
The task instance unit 330 is composed of a plurality of individually executable components, and includes a plurality of task sub-units 331, each of which is a minimum executable unit and represents different task contents.
Task sub-unit containing
And the task processor object instance is used for scheduling by the execution unit, and after the task instance is started, the task information is automatically registered for unified management of the management center unit.
An RPC communication unit is arranged between the execution unit and the task instance unit, and an RPC communication protocol is contained in the RPC communication unit and used for maintaining a communication mechanism between the execution unit and the task instance unit.
The embodiment of the application also provides a task scheduling management method, which is used for executing any one of the management systems. Specifically, the developer uploads the jar package of the task instance SpringBoot developed by the developer through the management center.
When uploading is completed, the management center check checks the executor resources (hard disk resources, and the resource information is reported through the executor heartbeat packet), commands to issue a call to the executor interface, and informs the executor to start asynchronous downloading of the task instance jar packet.
And the management center issues a command by calling a restful interface of the executor, the executor end local machine maintains an MQ download queue thread pool, and when the management center download command is received, the asynchronous download thread is started to download the jar file of the remote task instance.
When the asynchronous downloading of the executor is completed, the Advice is sent to inform the management center that the asynchronous downloading is completed, the management center matches information, records the corresponding information into a warehouse for the interface end to check and manage, and the management center achieves the automatic management of the remote control Task instance by issuing commands of starting, stopping and the like, including the execution command of the Task instance and the like.
Task management: after the Task instance is started, a plurality of tasks in the Task instance are automatically registered through a Restful interface of a management center, a management end can dynamically configure the scheduling time of the Task instance through the interface, and the aim of remotely managing the Task instance is achieved by issuing commands of starting, stopping, deleting, updating and the like through the commands.
Scheduling logs: when the management center is abnormal and the asynchronous execution log is called back and fails, the serialized log information of the machine is processed by an actuator asynchronous daemon thread (the serialized log catalog is scanned at fixed time and reported to the management center (normal)).
The present application is, with respect to the prior art:
1. configuring task parameters and task scheduling on a visual interface;
2. standardizing a standard RESTful task interface, providing a platform-level task scheduling center, and improving the development efficiency of engineers;
3. the task execution log is recorded, the log is conveniently tracked by related responsible persons, an early warning threshold value is provided, different early warning mechanisms are dynamically configured, and the method is flexible and universal.
4. And the cluster deploys the task executor to ensure high availability of the task.
5. And a disaster recovery mechanism is independently researched and developed, the state of a task executor is monitored through a heartbeat packet, a platform automatically processes a disaster recovery server, faults are transferred, the task is guaranteed not to be down, and the usability of a program is improved.
6. The method has the advantages that a gray scale upgrading mechanism is realized, the concept of version numbers is provided, developers can smoothly upgrade the task version, dynamic routing strategies are configured on the bottom layer through Socket communication, the purpose of smooth upgrading is achieved, and the situations of task execution loss and the like caused by upgrading are avoided.
Fig. 3 is a schematic structural diagram of an identification device according to an embodiment of the present application. The object detection apparatus 4000 comprises a processor 41 and may further comprise an input device 42, an output device 43 and a memory 44. The input device 42, the output device 43, the memory 44, and the processor 41 are connected to each other via a bus.
The memory includes, but is not limited to, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), which is used for storing instructions and data.
The input means are for inputting data and/or signals and the output means are for outputting data and/or signals. The output means and the input means may be separate devices or may be an integral device.
The processor may include one or more processors, for example, one or more Central Processing Units (CPUs), and in the case of one CPU, the CPU may be a single-core CPU or a multi-core CPU. The processor may also include one or more special purpose processors, which may include GPUs, FPGAs, etc., for accelerated processing.
The memory is used to store program codes and data of the network device.
The processor is used for calling the program codes and data in the memory and executing the steps in the method embodiment. Specifically, reference may be made to the description of the method embodiment, which is not repeated herein.
It will be appreciated that fig. 3 only shows a simplified design of the object detection device. In practical applications, the motion recognition devices may also respectively include other necessary components, including but not limited to any number of input/output devices, processors, controllers, memories, etc., and all motion recognition devices that can implement the embodiments of the present application are within the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the division of the unit is only one logical function division, and other division may be implemented in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. The shown or discussed mutual coupling, direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some interfaces, and may be in an electrical, mechanical or other form.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on or transmitted over a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)), or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a read-only memory (ROM), or a Random Access Memory (RAM), or a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, a magnetic disk, or an optical medium, such as a Digital Versatile Disk (DVD), or a semiconductor medium, such as a Solid State Disk (SSD).
Although the preferred embodiments of the present invention have been described in detail, the present invention is not limited to the details of the foregoing embodiments, and various equivalent changes (such as number, shape, position, etc.) may be made to the technical solution of the present invention within the technical spirit of the present invention, and the equivalents are protected by the present invention.
Claims (10)
1. A task scheduling management system, comprising:
the management center unit is used as an operation interface and used for issuing scheduling operation and command issuing operation of all tasks;
the execution unit is composed of individually operable components and used for receiving the command of the management center unit and sending the command to the task instance unit;
the task instance unit is composed of independent executable components and comprises a plurality of task sub-units, and each task sub-unit is a minimum executable unit and represents different task contents;
and a communication channel is arranged between the execution unit and the task force unit, and the execution unit is used for managing the operation of the task instance unit.
2. The task schedule management system of claim 1,
the management center unit is specifically used as a web end management interface of the task scheduling management system, can clearly check the state information of the currently managed task instance unit and the executing unit, is provided with an external standard restful interface, and is called by the executing unit and the task instance unit.
3. The task schedule management system of claim 1,
the management center unit judges whether all task nodes under the current execution unit are normal or not through heartbeat packet monitoring, judges that the current service is unavailable under the condition that a target node does not respond in a configuration rule, completely migrates all task nodes under the execution unit to a server corresponding to another available execution unit through a fault transfer mechanism, and starts all current backup task nodes.
4. The task schedule management system of claim 1,
the execution unit adopts a dynamic routing strategy to achieve connection management of different task instance versions, when the management center unit designates a new version, the execution unit monitors that the new version is available, the task executes and calls Socket connection of the new version to carry out communication, the purpose of calling a new task is achieved, excessive gray scale upgrading is completed under the condition of no restarting, and after the dynamic routing strategy finds the new connection, the execution unit automatically closes an old version task instance.
5. The task schedule management system of claim 1,
the task sub-unit comprises
And the task processor object instance is used for scheduling by the execution unit, and after the task instance is started, the task information is automatically registered for unified management of the management center unit.
6. The task schedule management system of claim 1,
and an RPC communication unit is arranged between the execution unit and the task instance unit, and an RPC communication protocol is contained in the execution unit and used for maintaining a communication mechanism between the execution unit and the task instance unit.
7. A task scheduling management method is characterized by comprising the following steps:
acquiring a jar package of a developed task instance SpringBoot, and uploading the jar package through a management center;
the management center checks the actuator resource, issues a command to call an actuator interface, and informs the actuator to start asynchronous downloading of a task instance jar packet;
after the Task instance is started, a plurality of tasks in the Task instance are automatically registered through a Restful interface of a management center, the management center dynamically configures the scheduling time of the Task instance through the interface, and the remote management of the Task instance is realized by issuing start, stop, deletion and update commands through commands;
after the Task instance completes Task execution, reporting the complete execution log through a Restful interface provided by a management center
For in management
Boundary of China
Checking; when the asynchronous execution log callback fails due to the exception of the management center, the serialized log information of the machine is processed by an actuator asynchronous daemon thread.
8. The task schedule management method of claim 7,
the management center issues a command by calling a restful interface of the executor, the executor end local machine maintains an MQ downloading queue thread pool, and when the management center downloading command is received, an asynchronous downloading thread is started to download a jar file of the remote task instance;
after the executor completes asynchronous downloading, it sends an Advice notification to manage
Has been downloaded and managed
Matching information, recording the corresponding information
And the library is used for the interface end to check and manage.
9. A management device comprising a memory having computer-executable instructions stored thereon and a processor that implements the system of any one of claims 1-6 when executing the computer-executable instructions on the memory.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the system of any one of the preceding claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911260131.2A CN111143044B (en) | 2019-12-10 | 2019-12-10 | Task scheduling management system, method, device and storage medium thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911260131.2A CN111143044B (en) | 2019-12-10 | 2019-12-10 | Task scheduling management system, method, device and storage medium thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111143044A true CN111143044A (en) | 2020-05-12 |
| CN111143044B CN111143044B (en) | 2023-08-29 |
Family
ID=70518040
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911260131.2A Active CN111143044B (en) | 2019-12-10 | 2019-12-10 | Task scheduling management system, method, device and storage medium thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143044B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112052222A (en) * | 2020-08-31 | 2020-12-08 | 康键信息技术（深圳）有限公司 | Heterogeneous object storage cluster access method, device, equipment and storage medium |
| CN112486656A (en) * | 2020-12-10 | 2021-03-12 | 上海创远仪器技术股份有限公司 | Method for realizing wireless ionization wire task scheduling and data downloading |
| CN112965794A (en) * | 2021-02-19 | 2021-06-15 | 西安智周深鉴信息科技集团有限公司 | Algorithm calling method, electronic device and storage medium |
| CN114138434A (en) * | 2021-11-19 | 2022-03-04 | 苏州浪潮智能科技有限公司 | Big data task scheduling system |
| CN115933565A (en) * | 2022-12-23 | 2023-04-07 | 广东职业技术学院 | AGV task exchange method, device, system and medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110029673A1 (en) * | 2009-07-31 | 2011-02-03 | Devendra Rajkumar Jaisinghani | Extensible framework to support different deployment architectures |
| CN103677973A (en) * | 2013-09-01 | 2014-03-26 | 西安重装渭南光电科技有限公司 | Distributed multi-task scheduling management system |
| US9866433B1 (en) * | 2015-11-23 | 2018-01-09 | Pivotal Software, Inc. | Light-weight cloud application platform |
| CN107766136A (en) * | 2017-09-30 | 2018-03-06 | 南威软件股份有限公司 | A kind of method of task cluster management and running |
| WO2018195899A1 (en) * | 2017-04-28 | 2018-11-01 | Beijing Didi Infinity Technology And Development Co., Ltd. | System and method for task scheduling and device management |
| US20190034224A1 (en) * | 2017-07-31 | 2019-01-31 | Vmware, Inc. | Systems and methods for task processing in a distributed environment |
| CN109408210A (en) * | 2018-09-27 | 2019-03-01 | 北京车和家信息技术有限公司 | Distributed timing task management method and system |
| CN109656698A (en) * | 2018-12-14 | 2019-04-19 | 平安城市建设科技(深圳)有限公司 | Task processing method, management platform, actuating station and computer readable storage medium |
-
2019
- 2019-12-10 CN CN201911260131.2A patent/CN111143044B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110029673A1 (en) * | 2009-07-31 | 2011-02-03 | Devendra Rajkumar Jaisinghani | Extensible framework to support different deployment architectures |
| CN103677973A (en) * | 2013-09-01 | 2014-03-26 | 西安重装渭南光电科技有限公司 | Distributed multi-task scheduling management system |
| US9866433B1 (en) * | 2015-11-23 | 2018-01-09 | Pivotal Software, Inc. | Light-weight cloud application platform |
| WO2018195899A1 (en) * | 2017-04-28 | 2018-11-01 | Beijing Didi Infinity Technology And Development Co., Ltd. | System and method for task scheduling and device management |
| US20190034224A1 (en) * | 2017-07-31 | 2019-01-31 | Vmware, Inc. | Systems and methods for task processing in a distributed environment |
| CN107766136A (en) * | 2017-09-30 | 2018-03-06 | 南威软件股份有限公司 | A kind of method of task cluster management and running |
| CN109408210A (en) * | 2018-09-27 | 2019-03-01 | 北京车和家信息技术有限公司 | Distributed timing task management method and system |
| CN109656698A (en) * | 2018-12-14 | 2019-04-19 | 平安城市建设科技(深圳)有限公司 | Task processing method, management platform, actuating station and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 刘一田;刘士进;: "多租户高可用并行任务调度框架", 计算机系统应用, no. 12 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112052222A (en) * | 2020-08-31 | 2020-12-08 | 康键信息技术（深圳）有限公司 | Heterogeneous object storage cluster access method, device, equipment and storage medium |
| CN112486656A (en) * | 2020-12-10 | 2021-03-12 | 上海创远仪器技术股份有限公司 | Method for realizing wireless ionization wire task scheduling and data downloading |
| CN112486656B (en) * | 2020-12-10 | 2022-12-16 | 上海创远仪器技术股份有限公司 | Method for realizing wireless ionization wire task scheduling and data downloading |
| CN112965794A (en) * | 2021-02-19 | 2021-06-15 | 西安智周深鉴信息科技集团有限公司 | Algorithm calling method, electronic device and storage medium |
| CN112965794B (en) * | 2021-02-19 | 2024-03-22 | 西安智周深鉴信息科技集团有限公司 | Algorithm calling method, electronic equipment and storage medium |
| CN114138434A (en) * | 2021-11-19 | 2022-03-04 | 苏州浪潮智能科技有限公司 | Big data task scheduling system |
| CN114138434B (en) * | 2021-11-19 | 2024-01-12 | 苏州浪潮智能科技有限公司 | Big data task scheduling system |
| CN115933565A (en) * | 2022-12-23 | 2023-04-07 | 广东职业技术学院 | AGV task exchange method, device, system and medium |
| CN115933565B (en) * | 2022-12-23 | 2023-10-20 | 广东职业技术学院 | AGV task exchange method, device, system and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111143044B (en) | 2023-08-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111143044A (en) | Task scheduling management system, method, device and storage medium thereof | |
| US10068015B2 (en) | Monitoring a monitoring-target process | |
| US9529613B2 (en) | Methods and apparatus to reclaim resources in virtual computing environments | |
| US8495573B2 (en) | Checkpoint and restartable applications and system services | |
| US20180351792A1 (en) | System and method for providing secure and redundant communications and processing for a collection of internet of things (iot) devices | |
| US9483314B2 (en) | Systems and methods for fault tolerant batch processing in a virtual environment | |
| EP1650653A2 (en) | Remote enterprise management of high availability systems | |
| US8782643B2 (en) | Device and method for controlling communication between BIOS and BMC | |
| CN110365762B (en) | Service processing method, device, equipment and storage medium | |
| US9753718B1 (en) | Non-disruptive upgrade including rollback capabilities for a distributed file system operating within a cluster of nodes | |
| EP2972824B1 (en) | Computer system using in-service software upgrade | |
| US10860364B2 (en) | Containerized management services with high availability | |
| CN115048205B (en) | ETL scheduling platform, deployment method thereof and computer-readable storage medium | |
| CN113422692A (en) | Method, device and storage medium for detecting and processing node faults in K8s cluster | |
| US11226808B2 (en) | Application execution device, application execution method, and recording medium | |
| CN115941739A (en) | Inspection system and inspection method for Internet of things equipment | |
| CN116166413A (en) | Lifecycle management for workloads on heterogeneous infrastructure | |
| JP2009271858A (en) | Computing system and program | |
| CN114490416A (en) | Method and system for fault detection switching of workflow service and computer storage medium | |
| CN114416276A (en) | Scheduling method and device of equipment management service, electronic equipment and storage medium | |
| US20240095041A1 (en) | Peripheral device communication | |
| US20240111579A1 (en) | Termination of sidecar containers | |
| JP7461521B1 (en) | Method for building and installing a target driver on a computer - Patents.com | |
| JP7116318B2 (en) | Processing system, processing method, upper system, lower system, upper program and lower program | |
| WO2024002190A1 (en) | Monitor-based container adjustment method and device, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |