CN111143044B - 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
- CN111143044B CN111143044B CN201911260131.2A CN201911260131A CN111143044B CN 111143044 B CN111143044 B CN 111143044B CN 201911260131 A CN201911260131 A CN 201911260131A CN 111143044 B CN111143044 B CN 111143044B
- Authority
- CN
- China
- Prior art keywords
- task
- unit
- management center
- management
- execution
- 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.)
- Active
Links
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, a task scheduling management method, a task scheduling management device and a storage medium thereof, which are compared with the prior art: the visual interface configures task parameters and task scheduling; the standard task interface is standardized, a task scheduling center at a platform level is provided, and the development efficiency of engineers is improved; the task execution log is recorded, so that the related responsible person can conveniently track the log, 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; independently developing a disaster recovery mechanism, monitoring the state of a task executor through a heartbeat packet, automatically processing a disaster recovery server by a platform, transferring faults and improving the usability of a program; the method realizes a gray scale upgrading mechanism, provides a concept of version number, enables a developer to smoothly upgrade task versions, enables a bottom layer to configure a dynamic routing strategy through Socket communication, achieves the purpose of smooth upgrading, and avoids the occurrence of conditions such as task execution missing caused by upgrading.
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, conventional task scheduling frameworks, such as the quatertz framework, can address task log management issues and, upon arrival of a predetermined (scheduled) time, take care of the system executing (or notifying) other software components. quartz can be instantiated as a cluster of independent items (load balancing and fault tolerance). The quartz can execute exactly to a specific time by the cron expression, creating a new task class object for each execution.
Disclosure of Invention
In order to solve the technical problems, embodiments of the present application provide a task scheduling management system, a task scheduling management method, a task scheduling management device, and a 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 for issuing scheduling operation and command issuing operation of all tasks;
the execution unit is formed by independently operable components, is used for receiving the command of the management center unit and issuing the command to the task instance unit;
the task instance unit is formed by independently operable components and comprises a plurality of task subunits, wherein each task subunit is a minimum executable unit and represents different task contents;
and a communication channel is arranged between the execution unit and the task actual unit, and the execution unit is used for managing the operation of the task instance unit.
Further, the management center unit is specifically configured to be used as a web side management interface of the task scheduling management system, so that state information of the task instance unit and the execution unit which are currently managed can be clearly checked, and an external standard restful interface is provided and is called by the execution unit and the task instance unit.
Further, the management center unit monitors through the heartbeat packet to judge whether all task nodes under the current execution unit are normal, in the configuration rule, the target node judges that the current service is not available under the condition of not responding, all the task nodes under the execution unit are migrated to the server corresponding to the other available execution unit through the fault transfer mechanism, and all the backup task nodes under the current execution unit are started.
Further, 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 execution calls Socket connection of the new version to communicate, the purpose of calling a new task is achieved, gray scale upgrade is completed under the condition of no restarting, and after the dynamic routing strategy discovers the new connection, the execution unit automatically closes an old version task instance.
Further, the task sub-unit comprises a task processor object instance for the execution unit to dispatch, and after the task instance is started, task information is automatically registered for unified management by the management center unit.
Further, an RPC communication unit is arranged between the execution unit and the task instance unit, and an RPC communication protocol is arranged in the RPC communication unit for maintaining a communication mechanism between the execution unit and the task instance unit. May include:
a second aspect of the embodiment of the present application provides a task scheduling management method, including:
acquiring a jar packet of a developed task instance SpringBoot, and uploading the jar packet through a management center;
the management center checks the resource of the executor, and issues a command to call the executor interface to inform the executor to start asynchronous downloading of the task instance jar package;
when a Task instance is started, automatically registering a plurality of tasks in the Task instance through a Restful interface of a management center, dynamically configuring the scheduling time of the Task instance through the interface by the management center, and realizing remote management of the Task instance through command issuing start, stop, delete and update commands;
after Task instance execution completes Task, reporting the complete execution log to a center through a Restful interface provided by a management center for the interface of the management center to check; when the exception of the management center causes the failure of asynchronous execution log callback, the native serialization log information is processed by the asynchronous daemon of the executor.
Further, the management center issues a command by calling a restful interface of the executor, the executor terminal locally maintains an MQ downloading queue thread pool, and when receiving the download command of the management center, an asynchronous downloading thread is started to download a remote task instance jar file;
after the asynchronous downloading of the executor is completed, the device is sent to inform the management center that the downloading is completed, the management center matches information, and corresponding information is recorded and put in storage for the interface end to check and manage.
In a third aspect, an embodiment of the present application provides a management apparatus, including a memory having computer-executable instructions stored thereon, and a processor, which implements the system of the first aspect when executing the computer-executable instructions on the memory.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the system of the first aspect described above.
In the embodiment of the application, the task is centered and visualized, the operable web management interface is provided, the task is managed automatically, the standardized task interface is provided, and the development is rapid, simple, lightweight and easy to expand.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
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 following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be understood that the terms "comprises" and "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 application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification 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 the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In the prior art, tasks cannot be visualized, and management is inconvenient. The time rule is inconvenient to change, and the database time rule description needs to be synchronously changed. The quatertz cluster is used when all nodes run on the same server, all nodes will terminate when the server crashes, and the timing task will not be executed normally. The quartz cluster causes the influence of the nodes on the states of other nodes due to possible asynchronous clocks when the nodes are not on the same server.
Therefore, the task scheduling management system provided by the application comprises a management center unit 310, an execution unit 320 and a task instance unit 330.
The management center unit 310 is configured to serve as an operation interface, issue scheduling operations and command issuing operations of all tasks, and specifically serve as a web end management interface of a task scheduling management system, so that state information of a task instance unit and an execution unit which are currently managed can be checked clearly, and an external standard restful interface is provided and is called by the execution unit and the task instance unit.
The management center unit 310 monitors the heartbeat packet through the management center end to judge whether all task nodes under the current executor are normal, and in the configuration rule, the target node judges that the current service is unavailable under the condition of not responding, at the moment, all the task nodes under the executor are migrated to other available executor servers through a fault transfer mechanism, all the current backup task nodes are started, and the whole process platform automatically completes operations such as migration, starting the task nodes and the like, so that the normal operation of the execution condition of the task is ensured.
The management center unit 310 provides a version mechanism of a task instance, and automatically starts different version instances of the task instance through an actuator dynamic routing policy, task execution is performed through Socket communication between the actuator and the task instance, dynamic routing policy is adopted at the actuator end to achieve different task instance version connection management, when a new version is designated by the center end, the actuator monitors that the new version is available, at the moment, task execution calls Socket connection of the new version to perform communication, the purpose of calling a new task is achieved, gray scale upgrading is excessively completed under the condition that the whole process is not restarted any more, after the dynamic routing policy finds out new connection, the actuator automatically closes an old version task instance, server resources are saved, and the whole gray scale upgrading process is completed.
The execution unit 320 is formed as a separately executable component, and is configured to receive a command from the management center unit and issue the command to the task instance unit.
The executor is a bridge between the management center and the task instance, and when the management center issues the command to the executor, the executor facilitates complete remote call management through an RPC communication protocol in the task instance. The deployment operation of the executor needs to be realized in advance by a developer, and the deployment operation of the task instance is automatically managed and maintained through the executor.
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 execution calls Socket connection of the new version to communicate, the purpose of calling a new task is achieved, gray scale upgrade is completed under the condition of no restarting, and after the dynamic routing strategy discovers the new connection, the execution unit automatically closes an old version task instance.
The task instance unit 330 is formed as a single executable component, and includes a plurality of task sub-units 331, each of which is a minimum executable unit and represents different task contents.
The task sub-unit comprises a task processor object instance for the execution unit to dispatch, and after the task instance is started, the task information is automatically registered for the 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 arranged 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 packet of the self-developed task instance SpringBoot through the management center.
When the uploading is completed, the management center check checks the resource of the executor (hard disk resource, resource information is reported through the heartbeat packet of the executor), and the command is issued to call the executor interface to inform the executor to start asynchronously downloading the task instance jar packet.
The management center issues a command by calling a restful interface of the executor, the executor terminal locally maintains an MQ downloading queue thread pool, and when receiving the download command of the management center, an asynchronous downloading thread is started to download a remote task instance jar file.
When the asynchronous downloading of the executor is completed, the method sends an address to inform the management center that the downloading is completed, the management center matches information, corresponding information records are stored in 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 such as start, stop and the like, including executing commands of the Task instance and the like.
And (3) task management: when 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 end can dynamically configure the scheduling time of the Task instance through the interface, and the aim of remotely managing the Task instance is fulfilled by issuing commands such as starting, stopping, deleting and updating through the commands.
Scheduling log: when the abnormal management center causes asynchronous execution log callback failure, the local serialization log information is processed by an executor asynchronous daemon thread (periodically scanning the serialization log catalog and reporting the management center (normal)).
Compared with the prior art, the application has the following advantages:
1. the visual interface configures task parameters and task scheduling;
2. the standard RESTful task interface is standardized, a platform-level task scheduling center is provided, and the development efficiency of engineers is improved;
3. the task execution log is recorded, the related responsible person is convenient to track the log, the early warning threshold is provided, different early warning mechanisms are dynamically configured, and the method is flexible and universal.
4. The clusters deploy task executors to ensure high availability of tasks.
5. And a disaster recovery mechanism is independently developed, the state of a task executor is monitored through a heartbeat packet, a platform automatically processes a disaster recovery server, a fault is transferred, the task is ensured not to be down, and the usability of a program is improved.
6. The method realizes a gray scale upgrading mechanism, provides a concept of version number, enables a developer to smoothly upgrade task versions, enables a bottom layer to configure a dynamic routing strategy through Socket communication, achieves the purpose of smooth upgrading, and avoids the occurrence of conditions such as task execution missing caused by upgrading.
Fig. 3 is a schematic structural diagram of an identification device according to an embodiment of the present application. The object detection device 4000 comprises a processor 41 and may further comprise input means 42, output means 43 and a memory 44. The input device 42, the output device 43, the memory 44 and the processor 41 are interconnected by a bus.
The memory includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable read-only memory (erasable programmable read only memory, EPROM), or portable read-only memory (compact disc read to only memory, CD to ROM) for the associated instructions and data.
The input means is for inputting data and/or signals and the output means is for outputting data and/or signals. The output device and the input device may be separate devices or may be a single device.
A processor may include one or more processors, including for example one or more central processing units (central processing unit, CPU), which in the case of a 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 acceleration processing.
The memory is used to store program codes and data for the network device.
The processor is used to call the program code and data in the memory to perform the steps of the method embodiments described above. Reference may be made specifically to the description of the method embodiments, and no further description is given here.
It will be appreciated that fig. 3 shows only a simplified design of the object detection device. In practical applications, the motion recognition device may also include other necessary elements, including but not limited to any number of input/output devices, processors, controllers, memories, etc., and all the motion recognition devices that can implement the embodiments of the present application are within the protection scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the division of the unit is merely a logic function division, and there may be another division manner when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. The coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In the above embodiments, it may be implemented in whole or in part 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. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted across 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 a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a read-only memory (ROM), or a random-access memory (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 (digital versatile disc, DVD), or a semiconductor medium such as a Solid State Disk (SSD), or the like.
The preferred embodiments of the present application have been described in detail above, but the present application is not limited to the specific details of the above embodiments, and various equivalent changes (such as number, shape, position, etc.) may be made to the technical solution of the present application within the scope of the technical concept of the present application, and these equivalent changes all belong to the protection of the present application.
Claims (7)
1. A task scheduling management system, comprising:
the management center unit is used as an operation interface for issuing scheduling operation and command issuing operation of all tasks;
the execution unit is formed by independently operable components, is used for receiving the command of the management center unit and issuing the command to the task instance unit;
the task instance unit is formed by independently operable components and comprises a plurality of task subunits, wherein each task subunit is a minimum executable unit and represents different task contents;
a communication channel is arranged between the execution unit and the task actual unit, and the execution unit is used for managing the operation of the task instance unit;
the management center unit is specifically used as a web end management interface of the task scheduling management system, checks 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;
the management center unit monitors through the heartbeat packet, judges whether all task nodes under the current execution unit are normal, judges that the current service is unavailable under the condition that the target node does not respond in the configuration rule, and all the task nodes under the execution unit are migrated to the servers corresponding to other available execution units through the fault transfer mechanism, and starts all the current backup task nodes;
the execution unit adopts a dynamic routing strategy to achieve different task instance version connection management, when the management center unit designates a new version, the execution unit monitors that the new version is available, the task execution calls Socket connection of the new version to communicate, the purpose of calling a new task is achieved, gray scale upgrade is completed under the condition of no restarting, and after the dynamic routing strategy discovers the new connection, the execution unit automatically closes an old version task instance.
2. The task scheduling management system according to claim 1, wherein,
the task sub-unit comprises a plurality of task processor object instances for the execution unit to dispatch, and after the task instance is started, the task information is automatically registered for the unified management of the management center unit.
3. The task scheduling management system according to claim 1, wherein,
and an RPC communication unit is arranged between the execution unit and the task instance unit, and an RPC communication protocol is arranged in the RPC communication unit and used for maintaining a communication mechanism between the execution unit and the task instance unit.
4. A task scheduling management method, characterized by comprising:
acquiring a jar packet of a developed task instance SpringBoot, and uploading the jar packet through a management center;
the management center checks the resource of the executor, and issues a command to call the executor interface to inform the executor to start asynchronous downloading of the task instance jar package;
when a Task instance is started, automatically registering a plurality of tasks in the Task instance through a Restful interface of a management center, dynamically configuring the scheduling time of the Task instance through the interface by the management center, and realizing remote management of the Task instance through command issuing start, stop, delete and update commands;
after Task instance execution completes Task, reporting the complete execution log to a center through a Restful interface provided by the management center for the management center interface to check; when the abnormal management center causes the failure of asynchronous execution log callback, the native serialization log information is processed by an asynchronous daemon of an executor;
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;
the management center unit is specifically used as a web end management interface of the task scheduling management system, checks 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;
the management center unit monitors through the heartbeat packet, judges whether all task nodes under the current execution unit are normal, judges that the current service is unavailable under the condition that the target node does not respond in the configuration rule, and all the task nodes under the execution unit are migrated to the servers corresponding to other available execution units through the fault transfer mechanism, and starts all the current backup task nodes;
the execution unit adopts a dynamic routing strategy to achieve different task instance version connection management, when the management center unit designates a new version, the execution unit monitors that the new version is available, the task execution calls Socket connection of the new version to communicate, the purpose of calling a new task is achieved, gray scale upgrade is completed under the condition of no restarting, and after the dynamic routing strategy discovers the new connection, the execution unit automatically closes an old version task instance.
5. The task scheduling management method according to claim 4, wherein,
the management center sends a command by calling a restful interface of the executor, the executor terminal locally maintains an MQ downloading queue thread pool, and when receiving the download command of the management center, an asynchronous downloading thread is started to download a remote task instance jar file;
after the asynchronous downloading of the executor is completed, the device is sent to inform the management center that the downloading is completed, the management center matches information, and the corresponding information record library is used for the interface end to check and manage.
6. A management device comprising a memory having stored thereon computer executable instructions and a processor which when executing the computer executable instructions on the memory implements the system of any of claims 1-3.
7. A computer readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, implements the system of any of the preceding claims 1-3.
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 CN111143044A (en) | 2020-05-12 |
| CN111143044B true 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) |
Families Citing this family (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 |
| CN112486656B (en) * | 2020-12-10 | 2022-12-16 | 上海创远仪器技术股份有限公司 | Method for realizing wireless ionization wire task scheduling and data downloading |
| CN112965794B (en) * | 2021-02-19 | 2024-03-22 | 西安智周深鉴信息科技集团有限公司 | Algorithm calling method, electronic equipment and storage medium |
| CN114138434B (en) * | 2021-11-19 | 2024-01-12 | 苏州浪潮智能科技有限公司 | Big data task scheduling system |
| CN115933565B (en) * | 2022-12-23 | 2023-10-20 | 广东职业技术学院 | AGV task exchange method, device, system and medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9329951B2 (en) * | 2009-07-31 | 2016-05-03 | Paypal, Inc. | System and method to uniformly manage operational life cycles and service levels |
| US10540201B2 (en) * | 2017-07-31 | 2020-01-21 | Vmware, Inc. | Systems and methods for task processing in a distributed environment |
-
2019
- 2019-12-10 CN CN201911260131.2A patent/CN111143044B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
|---|
| 多租户高可用并行任务调度框架;刘一田;刘士进;;计算机系统应用(12);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111143044A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111143044B (en) | Task scheduling management system, method, device and storage medium thereof | |
| US8495573B2 (en) | Checkpoint and restartable applications and system services | |
| JP5579650B2 (en) | Apparatus and method for executing monitored process | |
| CN107016480B (en) | Task scheduling method, device and system | |
| EP1650653A2 (en) | Remote enterprise management of high availability systems | |
| US9483314B2 (en) | Systems and methods for fault tolerant batch processing in a virtual environment | |
| EP2972824B1 (en) | Computer system using in-service software upgrade | |
| US8266301B2 (en) | Deployment of asynchronous agentless agent functionality in clustered environments | |
| 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 | |
| CN109788068B (en) | Heartbeat state information reporting method, device and equipment and computer storage medium | |
| US10860364B2 (en) | Containerized management services with high availability | |
| CN111262908A (en) | Task construction method and system based on jenkins | |
| JP7161560B2 (en) | Artificial intelligence development platform management method, device, medium | |
| US11397632B2 (en) | Safely recovering workloads within a finite timeframe from unhealthy cluster nodes | |
| US10461991B1 (en) | Dynamic replication peering | |
| CN112559461A (en) | File transmission method and device, storage medium and electronic equipment | |
| JP2009271858A (en) | Computing system and program | |
| CN105791345A (en) | Communication system of server and industrial personal computer in semiconductor technological device | |
| CN114490416A (en) | Method and system for fault detection switching of workflow service and computer storage medium | |
| CN114816656A (en) | Container group migration method, electronic device and storage medium | |
| CN114189429A (en) | System, method, device and medium for monitoring server cluster faults | |
| CN113806051B (en) | Task management method and device of computing equipment, storage medium and computing equipment | |
| CN111078658B (en) | Method and device for mounting cluster file system | |
| CN110022220A (en) | Routing Activiation method and system in business card recognition |
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 |