CN110119306B - Method, device and equipment for balancing automatic scheduling of jobs and storage medium - Google Patents
Method, device and equipment for balancing automatic scheduling of jobs and storage medium Download PDFInfo
- Publication number
- CN110119306B CN110119306B CN201910432597.XA CN201910432597A CN110119306B CN 110119306 B CN110119306 B CN 110119306B CN 201910432597 A CN201910432597 A CN 201910432597A CN 110119306 B CN110119306 B CN 110119306B
- Authority
- CN
- China
- Prior art keywords
- task
- executed
- execution time
- starting
- determining
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/48—Indexing scheme relating to G06F9/48
- G06F2209/484—Precedence
Abstract
The application provides a method, a device, equipment and a storage medium for automatic job scheduling balancing. The automatic job scheduling balancing method comprises the following steps: determining that resource conflicts exist in resources required by a task to be executed; determining a starting optional time period corresponding to the task to be executed; determining an execution time capable of avoiding the resource conflict in the startup optional period; and starting the task to be executed according to the execution time. According to the method and the device, under the condition that resource conflict exists, the execution time period of the task to be executed is adjusted to be capable of avoiding the resource conflict through adjustment, so that the conflict between the tasks is effectively avoided through an automatic means, the one-time success rate of operation execution is improved, and the corresponding maintenance cost is effectively reduced.
Description
Technical Field
The application relates to the technical field of cloud computing, in particular to a method, a device, equipment and a storage medium for balancing automatic job scheduling.
Background
At present, after a cloud platform user sets a timing job, due to the problem of job quantity and the problem of authority, the user does not perform effective rebalancing evaluation operation on the set timing job, however, even if the user sets the timing job, the user is defined with a relatively reasonable execution time period or has no related resource conflict problem during definition, but with the continuous setting of other subsequent jobs, the execution environment of the job changes, and thus job conflicts are caused.
Disclosure of Invention
In view of this, the method, the apparatus, the device and the storage medium for job automatic scheduling balancing provided in the embodiments of the present application can avoid job conflicts.
In a first aspect, an embodiment of the present application provides a method for balancing job automatic scheduling, where the method includes: determining that resource conflicts exist in resources required by a task to be executed; determining a starting optional time period corresponding to the task to be executed; determining an execution time capable of avoiding the resource conflict in the startup optional period; and starting the task to be executed according to the execution time.
In the implementation process, when the resource conflict exists in the resource needed by the task to be executed, the starting optional time period corresponding to the task to be executed is determined, so that the execution time capable of avoiding the resource conflict is determined in the starting optional time period, the task to be executed is started according to the execution time, the conflict among the tasks is effectively avoided through an automatic means, the one-time success rate of operation execution is improved, and the corresponding maintenance cost is effectively reduced.
With reference to the first aspect, an embodiment of the present application provides a first possible implementation manner of the first aspect, and after determining a starting optional time period corresponding to the task to be executed, the method further includes: sending prompt information under the condition that the conflict cannot be avoided by adjusting the execution time of executing the task to be executed, wherein the prompt information is used for indicating that the resource conflict exists; wherein determining a task execution time capable of avoiding the resource conflict in the startup selectable time period comprises: determining, in the startup selectable period, an execution time that can avoid the resource conflict if it is determined that the conflict can be avoided by adjusting an execution time to execute the task to be executed.
In the implementation process, when it is determined that the conflict cannot be avoided by adjusting the execution time for executing the task to be executed, prompt information is sent out to inform workers of indicating that the resource conflict exists through the prompt information, and further the conflict is avoided in a manual mode. And determining the execution time capable of avoiding the resource conflict under the condition that the conflict can be avoided by adjusting the execution time for executing the task to be executed, so as to realize automatic conflict avoidance.
With reference to the first aspect or the first possible implementation manner of the first aspect, an embodiment of the present application provides a second possible implementation manner of the first aspect, and before determining that there is a resource conflict in resources required by a task to be executed, the method further includes: the method comprises the steps of obtaining tasks to be executed from task lists to be executed, wherein the task lists to be executed comprise a plurality of tasks to be executed, and the tasks to be executed in the task lists to be executed comprise at least one of the following tasks: conflicting tasks exist; a task newly built by a user; and the execution times reach a preset threshold value, and the task corresponding to the execution time condition is recorded.
In the implementation process, the task to be executed is acquired from the task list to be executed, and the task to be executed in the task list to be executed includes at least one of the following: conflicting tasks exist; a task newly built by a user; the execution times reach the preset threshold value and the tasks corresponding to the execution time conditions are recorded, so that more tasks to be executed can be subjected to conflict analysis, and further execution conflicts among the tasks to be executed can be effectively avoided.
With reference to the first aspect, an embodiment of the present application provides a third possible implementation manner of the first aspect, where after determining an execution time that can avoid the resource conflict in the starting optional period, before starting the task to be executed according to the execution time, the method further includes: acquiring the number of the tasks to be executed which are determined and adjusted; determining that the number is greater than or equal to a preset threshold; wherein, starting the task to be executed according to the execution time comprises: and starting all the tasks to be executed which are determined and adjusted according to the execution time when the number is larger than or equal to a preset threshold value.
In the implementation process, the number of the tasks to be executed which are determined and adjusted is obtained; and determining that the number is greater than or equal to a preset threshold value, so that when the number is greater than or equal to the preset threshold value, all the tasks to be executed which are determined and adjusted are started according to the execution time, and multiple jobs can be adjusted at one time, so that the adjustment efficiency of the tasks to be executed is improved, and the conflicts among the tasks are further effectively avoided.
With reference to the first aspect, an embodiment of the present application provides a fourth possible implementation manner of the first aspect, where determining that a resource conflict exists in a resource required by a task to be executed includes: acquiring resources corresponding to the task to be executed; judging whether the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed; and if so, representing that the resources required by the task to be executed have resource conflict.
In the implementation process, the resources corresponding to the tasks to be executed are obtained; judging whether the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed; when the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed, determining that the resource needed by the task to be executed has a resource conflict, and thus quickly and accurately determining whether the task to be executed currently has a conflict with other tasks.
With reference to the first aspect, an embodiment of the present application provides a fifth possible implementation manner of the first aspect, where the determining a starting optional time period corresponding to the task to be executed includes: querying a starting optional time period corresponding to the identification information of the task to be executed in a database, wherein the starting optional time period input by a user when the task to be executed is created and the corresponding relation between the starting optional time period and the identification information are stored in the database.
In the implementation process, the starting optional time interval corresponding to the identification information of the task to be executed is inquired from the database, so that the starting optional time interval can be quickly determined, the inquiry range is reduced, and the inquiry complexity is reduced.
With reference to the first aspect, an embodiment of the present application provides a sixth possible implementation manner of the first aspect, where the determining, in the starting optional time period, an execution time that can avoid the resource conflict includes: adjusting the execution time of executing the task to be executed within the starting optional time period; determining whether the adjusted execution time has a task which conflicts with the task to be executed; and if the task which conflicts with the task to be executed does not exist, determining the adjusted execution time as the execution time which can avoid the resource conflict.
In the implementation process, the execution time for executing the task to be executed is adjusted in the starting optional time period, so that on the premise of meeting the requirements of a user, an execution time is selected from the starting optional time period, whether a task which conflicts with the task to be executed exists in the adjusted execution time is determined, and if no task which conflicts with the task to be executed exists, the adjusted execution time is determined as the execution time which can avoid the resource conflict, so that the execution conflict between the tasks is avoided through the adjusted execution time.
With reference to the first aspect, an embodiment of the present application provides a seventh possible implementation manner of the first aspect, where the adjusting the execution time for executing the task to be executed within the starting optional time period includes: acquiring a preset execution time corresponding to the task to be executed, wherein the preset execution time is within the starting optional time period; dynamically adjusting the preset execution time forwards or backwards by taking the preset execution time as a starting point in the starting optional time period; and determining the adjusted preset execution time as the execution time for executing the task to be executed.
In the implementation process, by acquiring a preset execution time corresponding to a task to be executed, the preset execution time is dynamically adjusted forwards or backwards within the starting optional time period by taking the preset execution time as a starting point; and determining the adjusted preset execution time as the execution time for executing the task to be executed. And then the preset execution time of the tasks to be executed is adjusted so as to avoid the conflict among the tasks.
In a second aspect, an automatic job scheduling balancing apparatus provided in an embodiment of the present application includes: the first processing module is used for determining that resources needed by the task to be executed have resource conflict; the second processing module is used for determining a starting optional time period corresponding to the task to be executed; a third processing module, configured to determine, in the startup optional period, an execution time that can avoid the resource conflict; and the execution module is used for starting the task to be executed according to the execution time.
In combination with the second aspect, this application provides a first possible implementation manner of the second aspect, and the apparatus further includes: the prompt module is used for sending prompt information under the condition that the conflict cannot be avoided by adjusting the execution time of executing the task to be executed after the optional starting time period corresponding to the task to be executed is determined, and the prompt information is used for indicating that the resource conflict exists; the third processing module is further configured to determine, in the startup selectable period, an execution time capable of avoiding the resource conflict when it is determined that the conflict can be avoided by adjusting the execution time for executing the task to be executed.
With reference to the second aspect or the first possible implementation manner of the second aspect, an embodiment of the present application provides a second possible implementation manner of the second aspect, where the apparatus further includes an obtaining module, configured to obtain a task to be executed from a task list to be executed before it is determined that there is a resource conflict in resources required by the task to be executed, where the task list to be executed includes a plurality of tasks to be executed, and the tasks to be executed in the task list to be executed include at least one of: conflicting tasks exist; a task newly built by a user; and the execution times reach a preset threshold value, and the task corresponding to the execution time condition is recorded.
With reference to the second aspect, an embodiment of the present application provides a third possible implementation manner of the second aspect, where the apparatus further includes a fourth processing module, where the fourth processing module is configured to, after determining an execution time that can avoid the resource conflict in the optional starting time period, obtain, before starting the task to be executed according to the execution time, the determined and adjusted number of the tasks to be executed; determining that the number is greater than or equal to a preset threshold; and the execution module is further used for starting all the tasks to be executed which are determined and adjusted according to the execution time when the number is greater than or equal to a preset threshold value.
With reference to the second aspect, an embodiment of the present application provides a fourth possible implementation manner of the second aspect, where the first processing module is further configured to obtain a resource corresponding to the execution of the task to be executed; judging whether the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed; and if so, representing that the resources required by the task to be executed have resource conflict.
With reference to the second aspect, an embodiment of the present application provides a fifth possible implementation manner of the second aspect, where the second processing module is further configured to query a startup optional time period corresponding to the identification information of the task to be executed in a database, where the startup optional time period and a corresponding relationship between the startup optional time period and the identification information, which are input by a user when creating the task to be executed, are stored in the database.
With reference to the second aspect, an embodiment of the present application provides a sixth possible implementation manner of the second aspect, where the third processing module is further configured to adjust an execution time for executing the task to be executed within the optional starting time period; determining whether the adjusted execution time has a task which conflicts with the task to be executed; and if the task which conflicts with the task to be executed does not exist, determining the adjusted execution time as the execution time which can avoid the resource conflict.
With reference to the second aspect, an embodiment of the present application provides a seventh possible implementation manner of the second aspect, where the third processing module is further configured to obtain a preset execution time corresponding to the task to be executed, where the preset execution time is located in the optional start time period; dynamically adjusting the preset execution time forwards or backwards by taking the preset execution time as a starting point in the starting optional time period; determining the adjusted preset execution time as the execution time for executing the task to be executed; determining whether the adjusted execution time has a task which conflicts with the task to be executed; and if the task which conflicts with the task to be executed does not exist, determining the adjusted execution time as the execution time which can avoid the resource conflict.
In a third aspect, a terminal device provided in an embodiment of the present application includes: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method for job automatic scheduling balancing according to any one of the first aspect when executing the computer program.
In a fourth aspect, a storage medium is provided in an embodiment of the present application, where the storage medium has instructions stored thereon, and when the instructions are executed on a computer, the instructions cause the computer to execute the method for balancing automatic scheduling of jobs according to any one of the first aspect.
In a fifth aspect, an embodiment of the present application provides a computer program product, which when running on a computer, causes the computer to execute the method for balancing automatic job scheduling according to any one of the first aspect.
Additional features and advantages of the disclosure will be set forth in the description which follows, or in part may be learned by the practice of the above-described techniques of the disclosure, or may be learned by practice of the disclosure.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a flowchart of an automatic job scheduling balancing method according to an embodiment of the present disclosure;
fig. 2 is a flowchart of an automatic job scheduling balancing method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an automatic job scheduling balancing apparatus according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
The above-mentioned drawbacks in the prior art are considered by the applicant to be the result of practical and careful study, and therefore, the discovery process of the above-mentioned problems and the solutions proposed by the embodiments of the present application in the afternoon should be the contributions of the applicant to the present application in the process of the present application.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.
Please refer to fig. 1, which is a flowchart of an automatic job scheduling balancing method provided in an embodiment of the present application, and is applied to a cloud computing management platform (the cloud computing management platform is hereinafter referred to as a "cloud platform" for short, and is deployed inside a data center and used for virtualizing hardware capability of the data center and then providing the virtualized hardware capability to a user), it should be understood that the method shown in fig. 1 may be automatic job scheduling balancing execution, the apparatus may correspond to a terminal device shown in fig. 4 below, and the terminal device may be various devices capable of executing the method, such as a server or a cloud server, for example, the present application embodiment is not limited thereto, and specifically includes the following steps:
step S101, determining that resource conflict exists in the resources needed by the task to be executed.
It should be understood that the task to be executed may also be referred to as a job, or a job task, or a service, etc.
Optionally, the task to be executed is a timing task, and the timing task includes jobs for a general user and an administrator user, for example: the common user of the cloud platform defines and manages the timing type operation through the cloud platform interface, for example, a cloud host with the backup name of 'SHRegion 02-AZ 01-4875' at 22 days is set. The administrator of the cloud platform defines and manages the timing type operation through the cloud platform interface or in other non-interface forms (such as command line scripts and the like), for example, a task of cleaning system disk logs for all computing nodes in the cloud platform at 24 days is set.
It will be appreciated that the above-described timed tasks may have to be started at a fixed point in time, for example, at 22. Such as the electricity marketing industry 22 point start "second kill", etc.
Of course, the above-mentioned timing task may also be started to be executed within a specific time period. For example, it may be performed between 22:00 and 23: 30.
Alternatively, the resource may be a hardware resource, such as a CPU (Central Processing Unit), or other software resource, such as network bandwidth.
As an embodiment, step S101 includes: acquiring resources corresponding to the task to be executed; judging whether the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed; and if the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed, representing that the resource needed by the task to be executed has resource conflict.
As an implementation scenario, identification information of each task to be executed and information of a resource corresponding to the identification information are stored in the cloud platform. For example, the information of the resource may be a name of the resource or an ID of the resource, etc. By pre-storing the identification information of each task to be executed in the cloud platform and the information of the resource corresponding to the identification information, the resource corresponding to the task to be executed, namely the resource required for executing the task to be executed, can be found in the cloud platform according to the task to be executed.
Of course, in actual use, the cloud platform may only store the corresponding relationship between each task to be executed and the corresponding resource, so as to find the resource required for executing each task to be executed through the corresponding relationship.
Optionally, determining whether the resource is a forbidden resource of an execution resource corresponding to any task of the tasks other than the task to be executed, includes:
and determining whether the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed according to the use information of the resource, wherein the use information comprises each task to be executed and the use state of the resource.
Optionally, the use state refers to what state the resource is in when a certain task to be executed is executed. For example, the usage information of resource a includes: when executing task a, resource a must be in a running state; while performing task B, resource a must be in an off state.
For example, if task a to be executed must be in a running state and resource a must be in a running state while task B to be executed must be in a shutdown state, that is, resource a is a disabled resource of task B while task a is executed, there must be a task failure or a task block if task a and task B are executed simultaneously, that is, there is a deadlock conflict between task a and task B.
In the implementation process, the resources corresponding to the tasks to be executed are obtained; judging whether the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed; when the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed, determining that the resource conflict exists in the resource needed by the task to be executed, and thus quickly and accurately determining whether the conflict exists between the task to be executed and other tasks.
It should be noted that the embodiment of the present application may be adapted to determine whether a resource conflicts among a plurality of tasks to be executed simultaneously, or may determine whether a resource conflicts exist one by one.
In a possible embodiment, before step S101, the method for balancing automatic job scheduling provided in the embodiment of the present application further includes: the method comprises the steps of obtaining tasks to be executed from task lists to be executed, wherein the task lists to be executed comprise a plurality of tasks to be executed, and the tasks to be executed in the task lists to be executed comprise at least one of the following tasks: conflicting tasks exist; a task newly built by a user; and the execution times reach a preset threshold value, and the task corresponding to the execution time condition is recorded.
Optionally, the tasks to be executed in the task list to be executed may be updated in real time, for example, the task list to be executed is updated before the job automatic scheduling balancing method provided in the embodiment of the present application is executed.
Optionally, the task with conflict refers to that the cloud platform finds that the task has conflict with other tasks during execution, and randomly selects 1 task from the conflicting tasks. It is to be understood that the number of selection tasks is 1 by way of example only and not by way of limitation, although other numbers are possible.
Of course, in actual use, other methods may be used for selection, for example, selecting the task with the longest execution time among the conflicting tasks.
Optionally, the preset threshold may be set according to a user requirement, or may be set according to an operation resource of the cloud platform, which is not specifically limited herein.
For example, the preset threshold may be 2, or N times, where N is an integer greater than or equal to 2. Optionally, N is 7.
It should be noted that the cloud platform holds execution records of all set timing tasks, and the execution records include, but are not limited to, execution duration, resource consumption information during execution, and the like.
In the implementation process, a task to be executed is acquired from a task list to be executed, where the task list to be executed includes a plurality of tasks to be executed, and the task to be executed in the task list to be executed includes at least one of the following: conflicting tasks exist; a task newly built by a user; the execution times reach the preset threshold value and the tasks corresponding to the execution time conditions are recorded, so that more tasks to be executed can be subjected to conflict analysis, and further execution conflicts among the tasks to be executed can be effectively avoided.
Optionally, the obtaining the task to be executed from the task list to be executed includes: and filtering the tasks to be executed in the task list to be executed, and acquiring the tasks to be executed from the filtered task list to be executed.
Optionally, when the number of tasks to be executed in the task list to be executed is large (for example, more than 1000), the jobs meeting the partial condition may be filtered according to the business condition, so as to reduce the evaluation complexity. For example, a job whose historical execution time is less than 2 minutes is not included in the evaluation range, i.e., a job whose historical execution time is less than 2 minutes is filtered. Or randomly sampled or included in the evaluation range according to some conditions, such as the first M jobs with execution time from large to small, M being an integer greater than 1. It is to be understood that the above examples are illustrative only and not limiting.
Of course, the task to be executed in the task list to be executed may also be filtered in any one of the following manners, that is, the first manner: and filtering according to the preset adjustment priority of each task to be executed in the task list to be executed. For example, the division may be by the authority of the job definer: the job set by the administrator is preferentially evaluated and optimized before the job defined by the common user, so as to avoid conflict. The second method comprises the following steps: and filtering the tasks to be executed in the task list to be executed according to the length of the execution cycle interval of each task to be executed. For example, the tasks to be executed whose execution cycle intervals are greater than the preset time interval are filtered from the task list to be executed. For jobs with particularly long execution cycle intervals, such as timed jobs that are executed 1 time per month or even annually, they are filtered out of the list of tasks to be executed.
Alternatively, the preset time interval may be monthly or yearly.
Alternatively, the preset time interval may be set according to actual requirements, and is not specifically limited herein.
In the implementation process, the tasks to be executed in the task list to be executed are filtered, and the tasks to be executed are obtained from the filtered task list to be executed, so that the analysis amount of the tasks to be executed can be effectively reduced, on one hand, the processing resources can be saved, and on the other hand, the efficiency of analyzing conflicts can be improved.
And step S102, determining a starting optional time interval corresponding to the task to be executed.
Optionally, the starting selectable period is a selectable time period range for starting the task to be executed, for example, 10 to 11 points.
Optionally, the start selectable period is entered by the user when creating the task. For example, when the cloud platform sets a timing job, a corresponding information entry interface is provided, so that a user can register information of starting optional time periods of the task through the information entry interface as required.
As an embodiment, step S102 includes: querying a starting optional time period corresponding to the identification information of the task to be executed in a database, wherein the starting optional time period input by a user when the task to be executed is created and the corresponding relation between the starting optional time period and the identification information are stored in the database.
Optionally, the database may be a local database, or may be a database in a cloud platform. Here, the number of the carbon atoms is not particularly limited.
Optionally, the identification information is used to uniquely identify the task to be performed.
Alternatively, the identification information may be a character string, a single character, a combination of letters and numbers, or the like. Here, the number of the carbon atoms is not particularly limited.
In a possible embodiment, after step S102, the method for balancing automatic job scheduling provided by the embodiment of the present application further includes: sending prompt information under the condition that the conflict cannot be avoided by adjusting the execution time of executing the task to be executed, wherein the prompt information is used for indicating that the resource conflict exists; at this time, step S102 includes determining an execution time capable of avoiding the resource conflict in the startup selectable period, in a case where it is determined that the conflict can be avoided by adjusting the execution time to execute the task to be executed.
Optionally, the prompt information is sent out, so that the worker or the developer performs processing according to the prompt information, such as manual adjustment, to avoid the conflict. And determining the execution time capable of avoiding the resource conflict under the condition that the conflict can be avoided by adjusting the execution time for executing the task to be executed, so as to realize automatic conflict avoidance.
Alternatively, when it is determined that the conflict cannot be avoided by adjusting the execution time for executing the task to be executed, the conflict cannot be avoided by adjusting the execution time or the execution time can be adjusted, but the number of tasks that need to be adjusted exceeds a threshold.
Optionally, when it is determined that the conflict can be avoided by adjusting the execution time for executing the task to be executed, the conflict can be avoided when the execution time is adjusted and the number of tasks that need to be adjusted does not exceed the preset threshold, and then the actual adjustment is performed (i.e., when step S103 is executed, the actual adjustment of the task to be executed is calculated). For example, when it is determined that the number of to-be-executed tasks that need to be adjusted is X and X is smaller than a preset threshold, it is determined that the conflict can be avoided by adjusting the execution time for executing the to-be-executed tasks.
For example, assume that there are currently 3 tasks to be executed, which are task 1, task 2, and task 3, respectively, and the preset threshold is 2, at this time, task 1, task 2, and task 3 have already determined the execution time that can avoid the resource conflict, but since the number of tasks to be adjusted is already determined to be 3, that is, the tasks to be adjusted are task 1, task 2, and task 3, at this time, the number of tasks to be adjusted 3 that has already been determined to be greater than the preset threshold 2, it can be determined that the current situation is that the conflict cannot be avoided by adjusting the execution time for executing the task to be executed. If only one task in the 3 tasks is determined to be the task needing to be adjusted, the situation that the current task belongs to the situation that the conflict can be avoided by adjusting the execution time of executing the task to be executed can be determined as the number 1 of the tasks to be adjusted is determined to be smaller than the preset threshold value 2.
It is to be understood that the above description is intended to be illustrative, and not restrictive.
Alternatively, in the present application, each task to be executed in the task list to be executed may be analyzed one by one to determine whether a resource conflict exists, when a resource conflict exists, the conflict may be avoided by determining whether the execution time for executing the task to be executed can be adjusted, when it is determined that the conflict can be avoided by adjusting the execution time for executing the task to be executed, the task to be executed is marked as a task for determining adjustment, then steps S101 to S103 are repeatedly executed until the task to be executed is analyzed or when the number of tasks for which adjustment has been determined exceeds a preset threshold value, all tasks to be executed are re-analyzed (or evaluated), if the number of tasks for executing is analyzed and the number of tasks for which adjustment has been determined does not exceed the preset threshold value, step S104 is executed, namely, the real adjustment of the task to be executed is realized.
Of course, in actual use, a plurality of tasks to be executed may be analyzed simultaneously. For example, when a plurality of tasks to be executed are analyzed simultaneously, it is first determined whether each task to be executed has a resource conflict (i.e., step S101, it is determined that the resource needed by the task to be executed has a resource conflict); then, respectively determining a starting optional time period corresponding to each task to be executed (namely step S102); respectively determining the execution time capable of avoiding the resource conflict from the starting optional time interval of each task to be executed (namely step S103); then analyzing each task to be executed so as to mark the task to be executed as a task for determining adjustment when determining that the conflict can be avoided by adjusting the execution time of executing the task to be executed; then counting the number of the tasks to be executed which are determined to be adjusted currently, when the number does not exceed a preset threshold value, repeatedly executing the steps S101 to S103, and then counting the number of the tasks to be executed which are determined to be adjusted; if it is determined that the adjusted number of the tasks to be executed does not exceed the preset threshold value until all the tasks to be executed in the task list to be executed are analyzed, step S104 is performed to adjust all the tasks to be executed that have been determined to be adjusted.
It is to be understood that the above description is intended to be illustrative, and not restrictive.
In the present application, there may be a time difference between the execution time of step S104 and the execution time of step S101 to step S103. That is, steps S101 to S103 first predict the task to be executed, and then the actual adjustment is realized through step S104.
Alternatively, the preset threshold may be set according to the number of all tasks to be executed in the task list to be executed, for example, may be 5% of all tasks to be executed. It should be understood that the threshold is set to 5% of all tasks to be performed by way of example and not limitation, and the preset threshold may be other values.
In the implementation process, by setting the preset threshold value for adjusting the number of the tasks, the situation that the final adjustment effect is poor due to adjustment of a large proportion (or a large number) of the number of the tasks is avoided, so that the adjustment efficiency of the tasks to be executed is improved, and conflicts among the tasks are further effectively avoided.
Step S103, determining the execution time capable of avoiding the resource conflict in the starting optional time interval.
Optionally, the execution time is used for executing the task to be executed.
As an embodiment, step S103 includes: adjusting the execution time of executing the task to be executed within the starting optional time period; determining whether the adjusted execution time has a task which conflicts with the task to be executed; and if the task which conflicts with the task to be executed does not exist, determining the adjusted execution time as the execution time which can avoid the resource conflict. And if the task which conflicts with the task to be executed exists, sending prompt information, wherein the prompt information is used for indicating that the execution time which can avoid the resource conflict does not exist in the starting optional time period.
Optionally, the adjusting the execution time of executing the task to be executed within the starting optional period includes: acquiring a preset execution time corresponding to the task to be executed, wherein the preset execution time is within the starting optional time period; dynamically adjusting the preset execution time forwards or backwards by taking the preset execution time as a starting point in the starting optional time period; and determining the adjusted preset execution time as the execution time for executing the task to be executed.
Optionally, the preset execution time is a time for executing the task, which is created by the user when creating the task to be executed. And the preset execution time is stored in the cloud platform after being created by the user.
Optionally, a time interval between the execution time and the preset execution time is greater than a preset value.
Alternatively, the preset value may be 10 minutes. Generally, the preset value may be set according to a user requirement, or may be set according to an operation condition of the cloud platform, which is not specifically limited herein.
For example, assuming that the starting selectable time period is 10 to 12 points, and the preset execution time is 11 points, dynamically adjusting the preset execution time forward or backward within the starting selectable time period with the preset execution time as a starting point means that the preset execution time is dynamically adjusted forward or backward with the 11 points as a starting point, for example, adjusting to 10 points in minutes, adjusting forward by minutes and analyzing whether there is a conflict in the new starting time, if there is a conflict until the time is adjusted to 10 points, adjusting backward by taking the 11 points as a starting point, and of course, adjusting backward by minutes and analyzing whether there is a conflict in the new starting time. And if the task which conflicts with the task to be executed does not exist, determining the adjusted execution time as the execution time which can avoid the resource conflict. Assume adjustment to 10: at 30, there is no conflict, and at this time 10: 30 as execution time capable of avoiding the resource conflict.
Of course, in actual use, the adjustment may be randomly performed within the starting optional time period.
In the implementation process, by acquiring a preset execution time corresponding to the task to be executed, the preset execution time is dynamically adjusted forwards or backwards within the starting optional time period by taking the preset execution time as a starting point; and determining the adjusted preset execution time as the execution time for executing the task to be executed. And then the preset execution time of the tasks to be executed is adjusted so as to avoid the conflict among the tasks.
Optionally, the specific implementation process of determining whether the adjusted execution time has a task that conflicts with the task to be executed may refer to the description of step S101, and specifically refer to the description of the resource conflict. Here, the description is omitted.
And step S104, starting the task to be executed according to the execution time.
Optionally, starting the task to be executed according to the execution time includes: and starting the task to be executed according to the execution time corresponding to each task to be executed.
In a possible embodiment, after step S103 and before step S104, the method for balancing automatic scheduling of jobs according to the embodiment of the present application further includes: acquiring the number of the tasks to be executed which are determined and adjusted; determining that the number is greater than or equal to a preset threshold; at this time, step S104 includes: and when the number is greater than or equal to a preset threshold value, starting all the tasks to be executed which are determined and adjusted according to the execution time, namely respectively starting all the tasks to be executed which are determined and adjusted according to the execution time corresponding to each task to be executed.
Optionally, the task to be executed that has been determined to be adjusted refers to a task that can avoid a conflict after the execution time is adjusted.
Optionally, the setting of the preset threshold may refer to the description in step S102, and is not described herein again.
In the implementation process, the number of the tasks to be executed which are determined and adjusted is obtained; and determining that the number is greater than or equal to a preset threshold value, so that when the number is greater than or equal to the preset threshold value, all the tasks to be executed which are determined and adjusted are started according to the execution time, and multiple jobs can be adjusted at one time, so that the adjustment efficiency of the tasks to be executed is improved, and the conflicts among the tasks are further effectively avoided.
Optionally, when the number is smaller than the preset threshold, the step S101 is executed again.
In a possible embodiment, before step S104, the method for balancing automatic scheduling of jobs according to the embodiment of the present application further includes: sending notification information, wherein the notification information is used for notifying a user whether to execute automatic adjustment on a task set by the user; after receiving the determined adjustment instruction returned by the user, step S104 is executed.
For example, the notification information is displayed through a terminal (such as a computer) of a user or a display interface of the cloud platform, after the user views the notification information, an adjustment instruction is generated by clicking a determination button on the display interface or inputting adjustable information on the display interface, the adjustment instruction is further returned to the cloud platform through a network, and the cloud platform executes the automatic job scheduling balancing method provided by the embodiment of the application based on the adjustment instruction.
In the implementation process, the notification information is sent, so that after receiving the notification information, the user feeds back whether to execute the automatic adjustment task according to the notification information, namely the automatic adjustment task is executed after the user confirms the automatic adjustment task, and inconvenience brought to the user by 'automatic' adjustment can be effectively avoided.
Optionally, sending notification information includes: and determining whether the system operated by the cloud platform is an appointed system, and if so, sending notification information.
Alternatively, the system is specified to be set for the preview according to the importance of each system operated in the cloud platform. Such as production systems that are particularly important to users.
Optionally, the importance of the system may be set by the user when the cloud platform runs its own system, or may be determined by the cloud platform based on big data. Here, the number of the carbon atoms is not particularly limited.
Generally, whether the system operated is a designated system may be determined by the name or identification of the system operated in the cloud platform.
In the implementation process, the notification information is sent to the designated system, so that inconvenience brought to a user of the system or dissatisfaction of the user can be effectively avoided.
The foregoing describes the method for balancing job automatic scheduling in this embodiment of the present application with reference to fig. 1, and the following describes, by way of example and without limitation, the method for balancing job automatic scheduling in this embodiment of the present application in detail with reference to fig. 2. Specifically, some steps involved in fig. 2 may be referred to the description above, and the detailed description is appropriately omitted here. The method shown in fig. 2 comprises:
step S201, a task to be executed is acquired.
Step S202, querying resources required for executing the task to be executed.
Step S203, determine whether the required resource conflicts with other tasks.
Optionally, the specific implementation process of step S201 to step S203 may refer to the description in step S101, and is not described herein again.
Step S204, when the required resource conflicts with other tasks, inquiring the starting optional time interval input by the user when the task to be executed is defined.
Optionally, the step may refer to the description in step S102, and is not described herein again.
Step S205 determines whether a conflict can be avoided by adjusting the execution time point of the task to be executed.
Optionally, the step may refer to the description in step S103, and is not described herein again.
In step S206, if the conflict can be avoided by adjusting the execution time point of the task to be executed, the execution time is adjusted.
Optionally, for a specific implementation of adjusting the execution time point, reference may be made to the description in step S103, and details are not repeated here.
And step S207, if the conflict can not be avoided by adjusting the execution time point of the task to be executed, recording and submitting manual work for processing.
Step S208, inquiring whether the number of the determined adjusted tasks reaches the appointed upper limit.
Optionally, the upper limit is the preset threshold referred to above, and the description in step S102 is specifically referred to, and is not repeated here.
In step S209, all the tasks with the determined adjustments are validated when the upper limit of the contract is reached.
Optionally, all the tasks determined and adjusted are validated, that is, all the tasks determined and adjusted to be executed are respectively started according to the execution time corresponding to each task to be executed.
Optionally, when the agreed upper limit is not reached, step S201 is executed.
According to the automatic job scheduling balancing method provided by the embodiment of the application, when the resource conflict exists in the resource needed by the task to be executed, the optional starting time period corresponding to the task to be executed is determined, the execution time capable of avoiding the resource conflict is determined in the optional starting time period, the task to be executed is started according to the execution time, the conflict among the tasks is effectively avoided, the tasks can be normally executed, and the economic loss brought to a user is avoided.
Referring to fig. 3, fig. 3 shows a job automatic scheduling balancing apparatus in a one-to-one correspondence with the job automatic scheduling balancing method shown in fig. 1, it should be understood that the apparatus 300 corresponds to the method embodiments shown in fig. 1 to fig. 2, and can perform the steps related to the method embodiments, and the specific functions of the apparatus 300 can be referred to the description above, and the detailed description is omitted here as appropriate to avoid redundancy. The device 300 includes at least one software functional module that can be stored in a memory in the form of software or firmware (firmware) or solidified in an Operating System (OS) of the device 300. Specifically, the apparatus 300 includes:
the first processing module 310 is configured to determine that there is a resource conflict in resources required by the task to be executed.
The second processing module 320 is configured to determine a starting optional time period corresponding to the task to be executed.
A third processing module 330, configured to determine, in the startup optional period, an execution time capable of avoiding the resource conflict.
And the execution module 340 is configured to start the task to be executed according to the execution time.
In a possible embodiment, the apparatus further comprises: the prompt module is used for sending prompt information under the condition that the conflict cannot be avoided by adjusting the execution time of executing the task to be executed after the optional starting time period corresponding to the task to be executed is determined, and the prompt information is used for indicating that the resource conflict exists; at this time, the third processing module 330 is further configured to, in the starting optional period, determine an execution time capable of avoiding the resource conflict when it is determined that the conflict can be avoided by adjusting the execution time for executing the task to be executed.
In a possible embodiment, the apparatus further includes an obtaining module, configured to obtain a task to be executed from a task list to be executed before it is determined that there is a resource conflict in resources required by the task to be executed, where the task list to be executed includes a plurality of tasks to be executed, and the task to be executed in the task list to be executed includes at least one of: conflicting tasks exist; a task newly built by a user; and the execution times reach a preset threshold value, and the task corresponding to the execution time condition is recorded.
In a possible embodiment, the apparatus further includes a fourth processing module, where the fourth processing module is configured to, after determining an execution time that can avoid the resource conflict in the startup optional period, obtain the number of the tasks to be executed that is determined and adjusted before starting the tasks to be executed according to the execution time; determining that the number is greater than or equal to a preset threshold; the execution module 340 is further configured to start all the tasks to be executed that are determined and adjusted according to the execution time when the number is greater than or equal to a preset threshold.
Optionally, the second processing module 320 is further configured to query a starting optional time period corresponding to the identification information of the task to be executed in a database, where the starting optional time period input by the user when creating the task to be executed and a corresponding relationship between the starting optional time period and the identification information are stored in the database.
Optionally, the third processing module 330 is further configured to adjust an execution time for executing the task to be executed within the starting optional time period; determining whether the adjusted execution time has a task which conflicts with the task to be executed; and if the task which conflicts with the task to be executed does not exist, determining the adjusted execution time as the execution time which can avoid the resource conflict.
Optionally, the third processing module 330 is further configured to obtain a preset execution time corresponding to the task to be executed, where the preset execution time is within the optional starting time period; dynamically adjusting the preset execution time forwards or backwards by taking the preset execution time as a starting point in the starting optional time period; determining the adjusted preset execution time as the execution time for executing the task to be executed; determining whether the adjusted execution time has a task which conflicts with the task to be executed; and if the task which conflicts with the task to be executed does not exist, determining the adjusted execution time as the execution time which can avoid the resource conflict.
Fig. 4 is a block diagram of a terminal device 500 in the embodiment of the present application, as shown in fig. 4. Terminal device 500 may include a processor 510, a communication interface 520, a memory 530, and at least one communication bus 540. Wherein the communication bus 540 is used for realizing direct connection communication of these components. The communication interface 520 of the device in the embodiment of the present application is used for performing signaling or data communication with other node devices. Processor 510 may be an integrated circuit chip having signal processing capabilities.
The Processor 510 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor 510 may be any conventional processor or the like.
The Memory 530 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 530 stores computer readable instructions, and when the computer readable instructions are executed by the processor 510, the terminal device 500 may perform the steps related to the embodiments of the methods in fig. 1 to 3.
Optionally, the terminal device 500 may further include a memory controller, an input output unit.
The memory 530, the memory controller, the processor 510, the peripheral interface, and the input/output unit are electrically connected to each other directly or indirectly, so as to implement data transmission or interaction. For example, these elements may be electrically coupled to each other via one or more communication buses 540. The processor 510 is configured to execute executable modules stored in the memory 530, such as software functional modules or computer programs included in the terminal device 500. And, the terminal device 500 is configured to perform the following method: determining that resource conflicts exist in resources required by a task to be executed; determining a starting optional time period corresponding to the task to be executed; determining an execution time capable of avoiding the resource conflict in the startup optional period; and starting the task to be executed according to the execution time.
The input and output unit is used for providing a task for a user to create and start an optional time period or preset execution time for the task creation so as to realize the interaction between the user and the server. The input/output unit may be, but is not limited to, a mouse, a keyboard, and the like.
Alternatively, the terminal device 500 may be a cloud server, and the cloud platform described above may be deployed in the cloud server.
It is to be understood that the structure shown in fig. 4 is merely illustrative, and the terminal device 500 may include more or fewer components than shown in fig. 4, or have a different configuration than shown in fig. 4. The components shown in fig. 4 may be implemented in hardware, software, or a combination thereof.
The embodiment of the present application further provides a storage medium, where the storage medium stores instructions, and when the instructions are run on a computer, when the computer program is executed by a processor, the method in the method embodiment is implemented, and in order to avoid repetition, details are not repeated here.
The present application also provides a computer program product which, when run on a computer, causes the computer to perform the method of the method embodiments.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by hardware, or by software plus a necessary general hardware platform, and based on such understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the method of the various implementation scenarios of the present application.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Claims (10)
1. A job automatic scheduling balancing method is characterized by comprising the following steps:
determining that resource conflicts exist in resources required by a task to be executed;
determining a starting optional time period corresponding to the task to be executed;
determining an execution time capable of avoiding the resource conflict in the startup optional period;
starting the task to be executed according to the execution time;
wherein the determining of the optional starting time period corresponding to the task to be executed includes:
querying a starting optional time period corresponding to the identification information of the task to be executed in a database, wherein the starting optional time period input by a user when the task to be executed is created and the corresponding relation between the starting optional time period and the identification information are stored in the database.
2. The method of claim 1, wherein after determining the selectable period of time for which the task to be executed corresponds to the activation, the method further comprises:
sending prompt information under the condition that the conflict cannot be avoided by adjusting the execution time of executing the task to be executed, wherein the prompt information is used for indicating that the resource conflict exists;
wherein determining a task execution time capable of avoiding the resource conflict in the startup selectable time period comprises:
determining, in the startup selectable period, an execution time that can avoid the resource conflict if it is determined that the conflict can be avoided by adjusting an execution time to execute the task to be executed.
3. The method according to claim 1 or 2, wherein before determining that there is a resource conflict with resources required by the task to be performed, the method further comprises:
the method comprises the steps of obtaining tasks to be executed from task lists to be executed, wherein the task lists to be executed comprise a plurality of tasks to be executed, and the tasks to be executed in the task lists to be executed comprise at least one of the following tasks:
conflicting tasks exist;
a task newly built by a user;
and the execution times reach a preset threshold value, and the task corresponding to the execution time condition is recorded.
4. The method according to claim 1, wherein after determining an execution time capable of avoiding the resource conflict in the starting optional period, before starting the task to be executed according to the execution time, the method further comprises:
acquiring the number of the tasks to be executed which are determined and adjusted;
determining that the number is greater than or equal to a preset threshold;
wherein, starting the task to be executed according to the execution time comprises:
and starting all the tasks to be executed which are determined and adjusted according to the execution time when the number is larger than or equal to a preset threshold value.
5. The method of claim 1, wherein determining that there is a resource conflict with resources required by the task to be performed comprises:
acquiring resources corresponding to the task to be executed;
judging whether the resource is a forbidden resource of an execution resource corresponding to any task of other tasks except the task to be executed;
and if so, representing that the resources required by the task to be executed have resource conflict.
6. The method of claim 1, wherein determining an execution time that can avoid the resource conflict in the startup selectable period comprises:
adjusting the execution time of executing the task to be executed within the starting optional time period;
determining whether the adjusted execution time has a task which conflicts with the task to be executed;
and if the task which conflicts with the task to be executed does not exist, determining the adjusted execution time as the execution time which can avoid the resource conflict.
7. The method of claim 6, wherein said adjusting an execution time for executing the task to be executed within the startup selectable time period comprises:
acquiring a preset execution time corresponding to the task to be executed, wherein the preset execution time is within the starting optional time period;
dynamically adjusting the preset execution time forwards or backwards by taking the preset execution time as a starting point in the starting optional time period;
and determining the adjusted preset execution time as the execution time for executing the task to be executed.
8. An apparatus for balancing automatic scheduling of jobs, the apparatus comprising:
the first processing module is used for determining that resources needed by the task to be executed have resource conflict;
the second processing module is used for determining a starting optional time period corresponding to the task to be executed;
the second processing module is specifically configured to query a starting optional time period corresponding to the identification information of the task to be executed in a database, where the starting optional time period input by a user when creating the task to be executed and a corresponding relationship between the starting optional time period and the identification information are stored in the database;
a third processing module, configured to determine, in the startup optional period, an execution time that can avoid the resource conflict;
and the execution module is used for starting the task to be executed according to the execution time.
9. A terminal device, comprising: memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method of job auto-scheduling balancing according to any one of claims 1 to 7 when executing the computer program.
10. A storage medium for storing instructions which, when executed on a computer, cause the computer to perform a method of job auto-scheduling balancing according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910432597.XA CN110119306B (en) | 2019-05-22 | 2019-05-22 | Method, device and equipment for balancing automatic scheduling of jobs and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910432597.XA CN110119306B (en) | 2019-05-22 | 2019-05-22 | Method, device and equipment for balancing automatic scheduling of jobs and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110119306A CN110119306A (en) | 2019-08-13 |
| CN110119306B true CN110119306B (en) | 2020-05-26 |
Family
ID=67522990
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910432597.XA Active CN110119306B (en) | 2019-05-22 | 2019-05-22 | Method, device and equipment for balancing automatic scheduling of jobs and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110119306B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110866613A (en) * | 2019-10-16 | 2020-03-06 | 中核核电运行管理有限公司 | Major repair preview method and device |
| CN110968590A (en) * | 2019-12-23 | 2020-04-07 | 北京奇艺世纪科技有限公司 | Task execution method and device, electronic equipment and computer readable storage medium |
| CN113094155B (en) * | 2019-12-23 | 2023-07-18 | 中国移动通信集团辽宁有限公司 | Task scheduling method and device under Hadoop platform |
| CN111158821B (en) * | 2019-12-26 | 2023-05-09 | 珠海金山数字网络科技有限公司 | Task processing method and device |
| CN113296874B (en) * | 2020-05-29 | 2022-06-21 | 阿里巴巴集团控股有限公司 | Task scheduling method, computing device and storage medium |
| CN111857995A (en) * | 2020-06-30 | 2020-10-30 | 海尔优家智能科技（北京）有限公司 | Process scheduling method and device, storage medium and electronic device |
| CN112181625A (en) * | 2020-10-12 | 2021-01-05 | 联通智网科技有限公司 | Task scheduling method, system, device, storage medium and computer equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106919445A (en) * | 2015-12-28 | 2017-07-04 | 华为技术有限公司 | A kind of method and apparatus of the container of Parallel Scheduling in the cluster |
| CN107241380A (en) * | 2016-03-29 | 2017-10-10 | 阿里巴巴集团控股有限公司 | For the method and apparatus of the load balancing adjusted based on the time |
| CN107291548A (en) * | 2016-03-31 | 2017-10-24 | 阿里巴巴集团控股有限公司 | The resource regulating method and device of task |
| CN109343941A (en) * | 2018-08-14 | 2019-02-15 | 阿里巴巴集团控股有限公司 | Task processing method, device, electronic equipment and computer readable storage medium |
| CN109634733A (en) * | 2018-12-13 | 2019-04-16 | 成都四方伟业软件股份有限公司 | Task scheduling and managing method, device and operation management server |
| CN109656693A (en) * | 2018-10-25 | 2019-04-19 | 中国平安人寿保险股份有限公司 | Method for scheduling task, device, server and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9003414B2 (en) * | 2010-10-08 | 2015-04-07 | Hitachi, Ltd. | Storage management computer and method for avoiding conflict by adjusting the task starting time and switching the order of task execution |
| CN106528275A (en) * | 2015-09-10 | 2017-03-22 | 网易（杭州）网络有限公司 | Processing method of data tasks and task scheduler |
| CN109783217B (en) * | 2019-01-22 | 2019-09-13 | 无锡华云数据技术服务有限公司 | Shut down determination method, apparatus, electronic equipment and the storage medium of period |
-
2019
- 2019-05-22 CN CN201910432597.XA patent/CN110119306B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106919445A (en) * | 2015-12-28 | 2017-07-04 | 华为技术有限公司 | A kind of method and apparatus of the container of Parallel Scheduling in the cluster |
| CN107241380A (en) * | 2016-03-29 | 2017-10-10 | 阿里巴巴集团控股有限公司 | For the method and apparatus of the load balancing adjusted based on the time |
| CN107291548A (en) * | 2016-03-31 | 2017-10-24 | 阿里巴巴集团控股有限公司 | The resource regulating method and device of task |
| CN109343941A (en) * | 2018-08-14 | 2019-02-15 | 阿里巴巴集团控股有限公司 | Task processing method, device, electronic equipment and computer readable storage medium |
| CN109656693A (en) * | 2018-10-25 | 2019-04-19 | 中国平安人寿保险股份有限公司 | Method for scheduling task, device, server and storage medium |
| CN109634733A (en) * | 2018-12-13 | 2019-04-16 | 成都四方伟业软件股份有限公司 | Task scheduling and managing method, device and operation management server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110119306A (en) | 2019-08-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110119306B (en) | Method, device and equipment for balancing automatic scheduling of jobs and storage medium | |
| US10264063B2 (en) | Method and apparatus for scheduling cloud server | |
| CN109117141B (en) | Method, device, electronic equipment and computer readable storage medium for simplifying programming | |
| US8875148B2 (en) | Product-specific system resource allocation within a single operating system instance | |
| US9588813B1 (en) | Determining cost of service call | |
| US8606905B1 (en) | Automated determination of system scalability and scalability constraint factors | |
| EP3935503B1 (en) | Capacity management in a cloud computing system using virtual machine series modeling | |
| CN107577527B (en) | Task generation and scheduling method and device | |
| CN111459629A (en) | Azkaban-based project operation method and device and terminal equipment | |
| CN115113987A (en) | Method, device, equipment and medium for allocating non-uniform memory access resources | |
| US11928461B2 (en) | Software utilization optimization in managed networks | |
| US20140059535A1 (en) | Software Inventory Using a Machine Learning Algorithm | |
| CN108733536B (en) | Monitoring management system and method | |
| US10637741B2 (en) | Instance usage facilitating system | |
| CN108521524B (en) | Agent collaborative task management method and device, computer equipment and storage medium | |
| JP2017129970A (en) | Management apparatus, management method, and management program | |
| CN110113434B (en) | Method, device and equipment for balancing automatic scheduling of jobs and storage medium | |
| JP5387083B2 (en) | Job management system and method | |
| CN114816583A (en) | Flink-based data automatic processing method and device and electronic equipment | |
| JP2015121963A (en) | Information processing system, monitoring method, and program | |
| US20150120940A1 (en) | Apparatus and method for changing resource using pattern information, and recording medium using the same | |
| CN113722141A (en) | Method and device for determining delay reason of data task, electronic equipment and medium | |
| CN110209548B (en) | Service control method, system, electronic device and computer readable storage medium | |
| CN112395081A (en) | Resource online automatic recovery method, system, server and storage medium | |
| CN113127221A (en) | Method, device, equipment and storage medium for limiting message consumption rate |
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 | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 214000, science and software park, Binhu District, Jiangsu, Wuxi 6 Patentee after: Huayun data holding group Co., Ltd Address before: 214000, science and software park, Binhu District, Jiangsu, Wuxi 6 Patentee before: WUXI CHINAC DATA TECHNICAL SERVICE Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |