Automatic elastic task scheduling method

Abstract

The invention discloses an automatic elastic task scheduling method, which realizes task scheduling by a Java timed task scheduling tool, and comprises the following steps of: before closing a service, storing or updating a scheduling task and related parameters thereof into a database; when the service is restarted, the stored scheduling task is taken out of the database, and if the scheduling task is triggered next time, the scheduling task is added into the task scheduler to be rescheduled after the rescheduling triggering time of the scheduling task is obtained according to the stored relevant parameters. According to the method, on the premise of ensuring the elastic scheduling, the service task can be closed without losing, and if the service is closed and the tracker is missed, thenext tracker time can also be calculated by restarting the service.

Description

technical field [0001] The invention relates to the field of task scheduling, in particular to an automatic flexible task scheduling method. Background technique [0002] Most of the current related task scheduling uses Spring's annotation technology or xml to directly write the Trigger type and Trigger time in the code, and then simply set the Trigger type and time to achieve the purpose of timing the trigger task. [0003] Although it is quite fast and simple to schedule scheduled tasks through Spring annotations and xml methods, and has the advantage of not losing tasks when the service is closed, it is not easy for users to frequently change the content of scheduled tasks such as Trigger type and Trigger time. , the code must be changed from time to time, less flexible. [0004] The Java scheduled task tool (Scheduler) can improve the inflexibility of the Spring scheduled task system, but the loss of tasks after closing the service is its shortcoming. When restarting th...

AI Technical Summary

Problems solved by technology

[0003] Although it is quite fast and simple to schedule scheduled tasks through Spring annotations and xml methods, and has the advantage of not losing tasks when the service is closed, it is not easy for users to frequently change the content of scheduled tasks such as Trigger type and Trigger time. , code must be changed frequently, less flexible

[0004] The Java scheduled task tool (Scheduler) can improve the inflexibility of the Spring scheduled task system, but the loss of tasks after closing the service is its shortcoming. When restarting the service, the user must manually reset the timing again. Task scheduling, if the number of scheduled tasks is set is too large, it will be time-consuming and inefficient. Even if the database is used for persistence, if the database records the next trigger time when the service is closed, the service cannot be restarted according to the originally set trigger time calculation. trigger time

Images