CN110336859B - Task scheduling system under multi-tenant environment - Google Patents
Task scheduling system under multi-tenant environment Download PDFInfo
- Publication number
- CN110336859B CN110336859B CN201910492362.XA CN201910492362A CN110336859B CN 110336859 B CN110336859 B CN 110336859B CN 201910492362 A CN201910492362 A CN 201910492362A CN 110336859 B CN110336859 B CN 110336859B
- Authority
- CN
- China
- Prior art keywords
- task
- information
- execution
- subsystem
- executor
- 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
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The task scheduling subsystem under the multi-tenant environment provided by the embodiment of the invention comprises a task arranging subsystem, a task scheduling subsystem and a task scheduling subsystem, wherein the task arranging subsystem is used for acquiring task information input by a user, generating a first task request, judging whether a first expression meets the requirement of the whole resource or not according to the meta-information of a task scheduler and the first expression, and sending the meta-information of a task executor and the first expression to the task scheduling subsystem when the first expression meets the requirement of the whole resource; the task scheduling subsystem is used for generating a first execution instruction and actuator parameter information according to the task actuator meta-information and the first expression and sending the first execution instruction and the actuator parameter information to the task execution subsystem; and the task execution subsystem is used for scheduling the task executors corresponding to the executor parameter information to work according to the first execution instruction and the executor parameter information, can expropriate all execution resources to the maximum extent, improves the number of tasks of each tenant in the window time, and ensures that the task allocation of each tenant is relatively fair.
Description
Technical Field
The invention relates to the technical field of enterprise application software, in particular to a task scheduling system in a multi-tenant environment.
Background
The business applied by the enterprise is complex and changeable, and the business data is processed more frequently. Compared with the personal application field, the method has more scenes needing task scheduling, so that the number of the scheduled tasks is more. Enterprise mobile applications have more complex business logic and data processing logic and have higher demand for scheduling resources than personal mobile applications.
The multi-tenant platform is a service, platform services can be provided for different tenants, resource management and control are achieved, resource isolation is achieved, and the platform can be protected by means of limiting resource contention of the tenants and the like. The distributed service can increase or reduce resources in the resource pool in a transverse expansion mode, so that the maximum utilization of the resources of the platform service is ensured, and the cost is saved.
The existing distributed timing scheduling has a set of mature system, but the attention point is put on resource control no matter scheduling algorithm or task calling, limited scheduling resources and execution resources of a multi-tenant shared scheduling platform are controlled, but the high requirements that the application scheduling quantity of enterprises is large and the service requirement is not limited cannot be met.
Disclosure of Invention
The embodiment of the invention aims to provide a task scheduling system under a multi-tenant environment, which can impose all execution resources to the maximum extent, improve the task quantity of each tenant in window time and ensure that the task distribution of each tenant is relatively fair.
In order to achieve the above object, an embodiment of the present invention provides a task scheduling system in a multi-tenant environment, including a task scheduling subsystem, and a task execution subsystem;
the task scheduling subsystem is used for acquiring task information input by a user and generating a first task request; the task information comprises task scheduler meta-information and task executor meta-information, and the first task request comprises a first expression;
the task scheduling subsystem is further configured to determine whether the first expression meets an overall resource requirement according to the task scheduler meta-information and the first expression, and send the task executor meta-information and the first expression to the task scheduling subsystem when the first expression meets the overall resource requirement;
the task scheduling subsystem is used for generating a first execution instruction and actuator parameter information according to the task actuator meta-information and the first expression, and sending the first execution instruction and the actuator parameter information to the task execution subsystem;
and the task execution subsystem is used for scheduling the task executor corresponding to the executor parameter information to work according to the first execution instruction and the executor parameter information.
Further, the task orchestration subsystem comprises a task management module and a task orchestration engine;
the task management module comprises a task management terminal and a task management server, wherein the task management terminal is used for acquiring task information input by a user, generating a first task request, reading all task information and resource information of a corresponding tenant from the task management server, and sending the first task request and all task information and resource information of the corresponding tenant to the task orchestration engine;
and the task orchestration engine is used for judging whether the first task request meets the overall resource requirement or not according to the first task request and all task information and resource information of the corresponding tenant, generating a first judgment result and feeding the first judgment result back to the task management module.
Further, if the first judgment result is not in accordance with the first judgment result, the task orchestration engine sends the first judgment result to the task management terminal to prompt a user that the request is invalid.
Further, the generation of the first determination result specifically includes:
the task arrangement engine performs hash processing on the first expression to generate a first trigger time window; wherein the time bit field of the trigger time window comprises year, month, day, hour, minute and second;
the task arranging engine traverses all tasks under the current tenant according to all task information and resource information of the corresponding tenant, judges whether an intersection exists between the first trigger time window and the trigger time window of the existing task, generates arranging success information if the intersection does not exist, and takes the arranging success information as the first judgment result;
if the intersection exists, the accumulator records +1, when the accumulator records do not reach a preset resource threshold value, arrangement success information is generated, and the arrangement success information is used as the first judgment result; and when the record of the accumulator reaches a preset resource threshold value, generating arrangement invalid information, and taking the arrangement invalid information as the first judgment result.
Furthermore, the task scheduling subsystem comprises a task trigger, a task execution adapter and a task execution management module;
the task trigger is used for generating a first trigger task request according to the first trigger time window and sending the first trigger task request to the task execution adapter in real time;
the task execution adapter is used for generating a first execution instruction and actuator parameter information according to the first trigger task request and the task actuator meta-information, and sending the first execution instruction and the actuator parameter information to a task execution subsystem;
the task execution adapter is also used for returning received information in real time when receiving the first trigger task request;
and the task execution management module is used for managing the task execution progress returned by the task execution adapter.
Further, the task execution subsystem comprises a task executor;
the task executor is an executor corresponding to the executor parameter information and performs interface adaptation with the task execution adapter for information transmission.
Further, the task executor communicates with the task execution adapter according to the communication rule and protocol of the task executor.
Further, the task executor is also used for synchronously feeding back the task execution progress to the task execution adapter;
wherein the task execution progress is a progress percentage.
Further, after receiving the task execution progress, the task execution adapter returns the task execution progress to the task execution management module in real time.
Further, when the task execution progress received by the task execution management module is 100%, the task execution adapter is released.
Compared with the prior art, the method has the following beneficial effects:
the task scheduling system under the multi-tenant environment comprises a task scheduling subsystem, a task scheduling subsystem and a task scheduling subsystem, wherein the task scheduling subsystem is used for acquiring task information input by a user, generating a first task request, judging whether a first expression meets the requirement of an overall resource or not according to the meta-information of a task scheduler and the first expression, and sending the meta-information of a task executor and the first expression to the task scheduling subsystem when the first expression meets the requirement of the overall resource; the task scheduling subsystem is used for generating a first execution instruction and actuator parameter information according to the task actuator meta-information and the first expression and sending the first execution instruction and the actuator parameter information to the task execution subsystem; and the task execution subsystem is used for scheduling the task executors corresponding to the executor parameter information to work according to the first execution instruction and the executor parameter information, can expropriate all execution resources to the maximum extent, improves the number of tasks of each tenant in the window time, and ensures that the task allocation of each tenant is relatively fair.
Drawings
FIG. 1 is a schematic structural diagram of an embodiment of a task scheduling system in a multi-tenant environment provided by the present invention;
FIG. 2 is a flowchart illustrating an embodiment of a task scheduling system in a multi-tenant environment.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. 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 invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of an embodiment of a task scheduling system in a multi-tenant environment provided by the present invention; the embodiment of the invention provides a task scheduling system under a multi-tenant environment, which comprises a task arranging subsystem, a task scheduling subsystem and a task executing subsystem, wherein the task arranging subsystem is used for arranging tasks;
the task scheduling subsystem is used for acquiring task information input by a user and generating a first task request; the task information comprises task scheduler meta-information and task executor meta-information, and the first task request comprises a first expression; the task scheduling subsystem is further configured to determine whether the first expression meets an overall resource requirement according to the task scheduler meta-information and the first expression, and send the task executor meta-information and the first expression to the task scheduling subsystem when the first expression meets the overall resource requirement; the task scheduling subsystem is used for generating a first execution instruction and actuator parameter information according to the task actuator meta-information and the first expression, and sending the first execution instruction and the actuator parameter information to the task execution subsystem; and the task execution subsystem is used for scheduling the task executor corresponding to the executor parameter information to work according to the first execution instruction and the executor parameter information.
It should be noted that the task scheduler meta information includes information related to task scheduling, such as task names and task expressions; the task executor meta-information includes information related to task execution, such as an executor name, an executor type, an executor characteristic (each kind of executor has its own characteristic attribute), and the like.
In the embodiment of the invention, the task orchestration subsystem comprises a task management module and a task orchestration engine;
the task management module comprises a task management terminal and a task management server, wherein the task management terminal is used for acquiring task information input by a user, generating a first task request, reading all task information and resource information of a corresponding tenant from the task management server, and sending the first task request and all task information and resource information of the corresponding tenant to the task orchestration engine; and the task orchestration engine is used for judging whether the first task request meets the overall resource requirement or not according to the first task request and all task information and resource information of the corresponding tenant, generating a first judgment result and feeding the first judgment result back to the task management module.
And if the first judgment result is not in accordance with the first judgment result, the task arranging engine sends the first judgment result to the task management terminal to prompt a user that the request is invalid.
It should be noted that the task management server stores all task configuration information and tenant resource configuration information of the tenant.
Preferably, the generating of the first judgment result specifically includes:
the task arrangement engine performs hash processing on the first expression to generate a first trigger time window; wherein the time bit field of the trigger time window comprises year, month, day, hour, minute and second;
the task arranging engine traverses all tasks under the current tenant according to all task information and resource information of the corresponding tenant, judges whether an intersection exists between the first trigger time window and the trigger time window of the existing task, generates arranging success information if the intersection does not exist, and takes the arranging success information as the first judgment result; if the intersection exists, the accumulator records +1, when the accumulator records do not reach a preset resource threshold value, arrangement success information is generated, and the arrangement success information is used as the first judgment result; and when the record of the accumulator reaches a preset resource threshold value, generating arrangement invalid information, and taking the arrangement invalid information as the first judgment result.
In this embodiment, the working principle of the task orchestration engine is as follows: and the task arranging engine receives the task arranging request, firstly carries out Hash processing on the scheduling expression of the new task, and extracts a time position domain in a time window, wherein the time position domain comprises month/week hour/minute. And traversing all tasks under the current tenant, comparing whether an intersection exists between the new task and the trigger time window of the existing task, and if the intersection exists, accumulating by a + 1. When the accumulator reaches the preset resource threshold value, the arrangement is informed to be invalid, otherwise, the arrangement is regarded as a valid task.
As a preferred embodiment of the present invention, the task scheduling subsystem includes a task trigger, a task execution adapter, and a task execution management module;
the task trigger is used for generating a first trigger task request according to the first trigger time window and sending the first trigger task request to the task execution adapter in real time; the task execution adapter is used for generating a first execution instruction and actuator parameter information according to the first trigger task request and the task actuator meta-information, and sending the first execution instruction and the actuator parameter information to a task execution subsystem; the task execution adapter is also used for returning received information in real time when receiving the first trigger task request; and the task execution management module is used for managing the task execution progress returned by the task execution adapter.
As another preferred embodiment of the present invention, the task execution subsystem includes a task executor;
the task executor is an executor corresponding to the executor parameter information and performs interface adaptation with the task execution adapter for information transmission.
In this embodiment, the task executor communicates with the task execution adapter according to the communication rule and protocol of the task executor. The task executor is also used for synchronously feeding back the task execution progress to the task execution adapter; wherein the task execution progress is a progress percentage.
And after receiving the task execution progress, the task execution adapter returns the task execution progress to the task execution management module in real time. And when the task execution progress received by the task execution management module is 100%, releasing the task execution adapter.
It should be noted that the heterogeneous task execution subsystem serves as a peripheral system, and the interfaces provided by the executors are different. The task execution adapter of the task scheduling subsystem is adapted for each interface, so that the task execution adapter and the task executor can communicate with each other according to the communication rule and protocol of the task executor.
The communication between the task trigger and the task execution adapter must be done in a specific "asynchronous manner": that is, after the task trigger informs the task execution adapter to trigger execution, the task execution adapter must immediately respond that the task trigger has received the request. The task execution action is executed in the background, and the execution progress or state is informed to the task execution management module in the execution process. In this scheme, the task execution system and the scheduling system must perform the task scheduling policy efficiently according to the above communication method.
In order to better illustrate the working principle of the invention, the following are specific examples:
as a preferred embodiment of the present invention, this embodiment shows a flow and an effect of a task scheduling engine performing resource prediction according to rules when a new task is created under the condition of an existing tenant task. In this embodiment, it is assumed that existing tenant tasks are within the same trigger time window and have reached the upper limit of the scheduling number, and therefore when a new task is created, it is predicted that an intersection exists and an invalidation is notified, and the specific process is as follows:
s1, assuming the time window for task execution is 1 second, the maximum scheduling number per tenant in the time window is 2. There are 2 tenant tasks, as follows:
s2, a task is newly established, which is specifically as follows:
s3, the task arrangement engine analyzes the three expressions and can measure the existing intersection. Namely: these 3 tasks may be triggered simultaneously at 00 hours 00 minutes 00 seconds per day in the future. Exceeding "maximum number of 2 schedules within time window", thus informing the new task of invalidity.
S4, other task expressions can be selected through the task management system, such as 01 second per minute. Therefore, after the task arrangement engine analyzes, the result can be obtained to be effective.
Referring to fig. 2, fig. 2 is a schematic flowchart of an embodiment of a task scheduling system in a multi-tenant environment, where the embodiment shows a data flow of a new task from task management to task scheduling to a task execution whole process:
step 1, supposing that a task is newly established by a task arranging subsystem, the task information is as follows:
| task name | Task expressions | Actuator type | Actuator parameters |
| Coffee brewing | 0 minute and 0 second per hour | Coffee machine interface | Italian style |
The scheduler meta information comprises a task name and a task expression, and the executor meta information comprises an executor type and an executor parameter; the task orchestration subsystem passes this information to the task triggers.
And 2, after receiving the information, the task trigger is arranged into a trigger queue according to the trigger condition defined by the task expression. The task expression (0 min 0 sec per hour) in this embodiment indicates that the task is expected to be executed in 00 min 00 sec per hour, and if the current time is 2019-01-0101: 05:05, the trigger time for the next execution is 2019-01-0102: 00: 00. And when 2019-01-0102: 00:00, the task trigger transmits the actuator meta-information (actuator type and actuator parameter) to the task execution adapter.
And 3, immediately informing the task trigger 'received' when the task execution adapter receives the executor meta-information. After receiving the received information, the task trigger releases the trigger, and waits for entering the next trigger time point, which is 2019-01-0103: 00:00 in this embodiment.
The task execution adapter now begins to perform actions in the background, step 4. The actuator adaptation is assembled according to the actuator type and parameters (in this embodiment, the actuator meta-information is "coffee machine interface/Italian"). The coffee machine in this embodiment has a remote control interface, the execution adapter calls the interface, the remote control coffee machine starts to cook espresso coffee, and feeds the cooking progress (cooking progress percentage) back to the task execution management module until the completion is completed, and the execution adapter is released.
In summary, the task scheduling system under the multi-tenant environment provided by the embodiment of the present invention includes a task scheduling subsystem, configured to obtain task information input by a user, generate a first task request, determine, according to the task scheduler meta-information and a first expression, whether the first expression meets an overall resource requirement, and send, when the first expression meets the overall resource requirement, the task executor meta-information and the first expression to the task scheduling subsystem; the task scheduling subsystem is used for generating a first execution instruction and actuator parameter information according to the task actuator meta-information and the first expression and sending the first execution instruction and the actuator parameter information to the task execution subsystem; and the task execution subsystem is used for scheduling the task executors corresponding to the executor parameter information to work according to the first execution instruction and the executor parameter information, can expropriate all execution resources to the maximum extent, improves the number of tasks of each tenant in the window time, and ensures that the task allocation of each tenant is relatively fair.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention.
Claims (8)
1. A task scheduling system under a multi-tenant environment is characterized by comprising a task arranging subsystem, a task scheduling subsystem and a task executing subsystem;
the task scheduling subsystem is used for acquiring task information input by a user and generating a first task request; the task information comprises task scheduler meta-information and task executor meta-information, and the first task request comprises a first expression;
the task scheduling subsystem is further configured to determine whether the first expression meets an overall resource requirement according to the task scheduler meta-information and the first expression, and send the task executor meta-information and the first expression to the task scheduling subsystem when the first expression meets the overall resource requirement;
the task scheduling subsystem is used for generating a first execution instruction and actuator parameter information according to the task actuator meta-information and the first expression, and sending the first execution instruction and the actuator parameter information to the task execution subsystem;
the task execution subsystem is used for scheduling a task executor corresponding to the executor parameter information to work according to the first execution instruction and the executor parameter information;
the task arranging subsystem comprises a task management module and a task arranging engine;
the task management module comprises a task management terminal and a task management server, wherein the task management terminal is used for acquiring task information input by a user, generating a first task request, reading all task information and resource information of a corresponding tenant from the task management server, and sending the first task request and all task information and resource information of the corresponding tenant to the task orchestration engine;
the task orchestration engine is used for judging whether the first task request meets the overall resource requirement or not according to the first task request and all task information and resource information of the corresponding tenant, generating a first judgment result and feeding the first judgment result back to the task management module; the generation of the first judgment result specifically includes:
the task arrangement engine performs hash processing on the first expression to generate a first trigger time window; wherein the time bit field of the trigger time window comprises year, month, day, hour, minute and second;
the task arranging engine traverses all tasks under the current tenant according to all task information and resource information of the corresponding tenant, judges whether an intersection exists between the first trigger time window and the trigger time window of the existing task, generates arranging success information if the intersection does not exist, and takes the arranging success information as the first judgment result;
if the intersection exists, the accumulator records +1, when the accumulator records do not reach a preset resource threshold value, arrangement success information is generated, and the arrangement success information is used as the first judgment result; and when the record of the accumulator reaches a preset resource threshold value, generating arrangement invalid information, and taking the arrangement invalid information as the first judgment result.
2. The task scheduling system under the multi-tenant environment of claim 1, wherein if the first determination result is inconsistent, the task orchestration engine sends the first determination result to the task management terminal to prompt a user that a request is invalid.
3. The task scheduling system in a multi-tenant environment of claim 1, wherein the task scheduling subsystem comprises a task trigger, a task execution adapter, and a task execution management module;
the task trigger is used for generating a first trigger task request according to the first trigger time window and sending the first trigger task request to the task execution adapter in real time;
the task execution adapter is used for generating a first execution instruction and actuator parameter information according to the first trigger task request and the task actuator meta-information, and sending the first execution instruction and the actuator parameter information to a task execution subsystem;
the task execution adapter is also used for returning received information in real time when receiving the first trigger task request;
and the task execution management module is used for managing the task execution progress returned by the task execution adapter.
4. The task scheduling system in a multi-tenant environment of claim 3, wherein the task execution subsystem includes a task executor;
the task executor is an executor corresponding to the executor parameter information and performs interface adaptation with the task execution adapter for information transmission.
5. The task scheduling system in a multi-tenant environment of claim 4, wherein the task executor communicates with the task execution adapter according to a communication rule and a protocol of the task executor.
6. The task scheduling system in a multi-tenant environment of claim 5, wherein the task executor is further configured to synchronously feed back a task execution progress to the task execution adapter;
wherein the task execution progress is a progress percentage.
7. The task scheduling system in a multi-tenant environment of claim 6, wherein the task execution adapter returns the task execution progress to the task execution management module in real time after receiving the task execution progress.
8. The task scheduling system in a multi-tenant environment according to claim 7, wherein the task execution adapter is released when the task execution progress received by the task execution management module is 100%.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910492362.XA CN110336859B (en) | 2019-06-06 | 2019-06-06 | Task scheduling system under multi-tenant environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910492362.XA CN110336859B (en) | 2019-06-06 | 2019-06-06 | Task scheduling system under multi-tenant environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110336859A CN110336859A (en) | 2019-10-15 |
| CN110336859B true CN110336859B (en) | 2020-04-07 |
Family
ID=68140933
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910492362.XA Active CN110336859B (en) | 2019-06-06 | 2019-06-06 | Task scheduling system under multi-tenant environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110336859B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112181621A (en) * | 2020-09-27 | 2021-01-05 | 中国建设银行股份有限公司 | Task scheduling system, method, equipment and storage medium |
| CN112631746A (en) * | 2020-12-08 | 2021-04-09 | 南方科技大学 | Service scheduling method and device, electronic equipment and storage medium |
| CN112559161A (en) * | 2021-02-19 | 2021-03-26 | 北京搜狐新媒体信息技术有限公司 | Task scheduling method and system |
| CN114416346B (en) * | 2021-12-23 | 2023-03-24 | 广州市玄武无线科技股份有限公司 | Multi-node task scheduling method, device, equipment and storage medium |
| CN116382814B (en) * | 2023-03-31 | 2024-03-12 | 杭州端点网络科技有限公司 | Unified system scheduling adaptation method, device, computer equipment and storage medium |
| CN116743876B (en) * | 2023-08-14 | 2023-12-08 | 云筑信息科技(成都)有限公司 | Method for realizing multi-tenant scheduling based on xxl-job |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103207807A (en) * | 2012-01-12 | 2013-07-17 | 阿里巴巴集团控股有限公司 | Task scheduling method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4074296B2 (en) * | 2005-03-25 | 2008-04-09 | 株式会社東芝 | Schedulability determination method, real-time system, and program |
| FR2949876B1 (en) * | 2009-09-08 | 2016-04-29 | Thales Sa | METHOD FOR REAL-TIME ORDERING OF A SET OF NON-CYCLIC MULTI-FRAME TASKS |
| CN103034475B (en) * | 2011-10-08 | 2015-11-25 | 中国移动通信集团四川有限公司 | Distributed Parallel Computing method, Apparatus and system |
| CN104657212B (en) * | 2015-02-13 | 2018-02-16 | 北京亚信数据有限公司 | A kind of method and system of task scheduling |
| CN107026900B (en) * | 2017-03-06 | 2020-02-14 | 浙江大华技术股份有限公司 | Shooting task allocation method and device |
-
2019
- 2019-06-06 CN CN201910492362.XA patent/CN110336859B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103207807A (en) * | 2012-01-12 | 2013-07-17 | 阿里巴巴集团控股有限公司 | Task scheduling method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110336859A (en) | 2019-10-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110336859B (en) | Task scheduling system under multi-tenant environment | |
| CN109271435B (en) | Data extraction method and system supporting breakpoint continuous transmission | |
| CN111338791A (en) | Method, device and equipment for scheduling cluster queue resources and storage medium | |
| US11210284B2 (en) | Method, system, apparatus, and computer-readable storage medium for sharing account resources | |
| CN113656157B (en) | Distributed task scheduling method and device, storage medium and electronic equipment | |
| US10884667B2 (en) | Storage controller and IO request processing method | |
| US20130332207A1 (en) | System and method for intelligent management of appointment waiting list | |
| CN106101080A (en) | Page access control method and device | |
| CN111507608B (en) | Work order early warning method and device and storage medium | |
| CN108196959B (en) | Resource management method and device of ETL system | |
| CN109901918B (en) | Method and device for processing overtime task | |
| CN111210340B (en) | Automatic task processing method, device, server and storage medium | |
| CN109885382A (en) | The system of cross-system distributed transaction processing method and distributing real time system | |
| CN109766316A (en) | File acquisition method, device, computer equipment and storage medium | |
| CN110750350B (en) | Large resource scheduling method, system, device and readable storage medium | |
| CN111626458A (en) | Processing method and device for user reservation request and related equipment | |
| CN116089040A (en) | Service flow scheduling method and device, electronic equipment and storage medium | |
| CN115048466A (en) | Data analysis method, system, terminal and storage medium | |
| CN115237577A (en) | Job scheduling method and device based on priority queue | |
| CN114116158A (en) | Task scheduling method and system based on SD-WAN system | |
| CN113238875A (en) | Queue-based request frequency control system and control method | |
| CN111522843B (en) | Control method, system, equipment and storage medium of data platform | |
| CN113656178A (en) | Data processing method, device, equipment and readable storage medium | |
| CN109214877B (en) | Order creation system, method, electronic device and computer-readable storage medium | |
| CN102693477B (en) | The disposal route of the meeting room application information of a kind of message and cooperative system |
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 | ||
| CP02 | Change in the address of a patent holder | ||
| CP02 | Change in the address of a patent holder |
Address after: 510000 room 23bd, No. 109, TIYU West Road, Tianhe District, Guangzhou City, Guangdong Province Patentee after: GUANGZHOU XUANWU WIRELESS TECHNOLOGY Co.,Ltd. Address before: 510620 unit 01, 32F, building B, Victoria Plaza, 103 TIYU West Road, Tianhe District, Guangzhou City, Guangdong Province Patentee before: GUANGZHOU XUANWU WIRELESS TECHNOLOGY Co.,Ltd. |