Distributed task scheduling method and system

Abstract

The invention belongs to the technical field of Internet, and discloses a distributed task scheduling method and system, and the method comprises the steps: enabling each node of a distributed task cluster to start self-registration, and registering task information which can be executed in each node; enabling each node to start a scheduling task at regular time, and obtaining task instances needing to be executed from a to-be-executed task instance set; and adding task instances needing to be executed into the distributed task pool of each node, and creating a plurality of threads for executing tasks by each node. According to the distributed task scheduling method provided by the invention, rapid and efficient execution of the distributed timed task is realized by reasonably utilizing resource regulation and control, and the system architecture is simple, convenient and easy to expand.

Description

technical field [0001] The invention belongs to the technical field of the Internet, and in particular relates to a distributed task scheduling method and system. Background technique [0002] In some commonly used software development systems at present, there are functions that need to be started spontaneously by the system at a specified time or frequency, and related processing is performed in the form of tasks. Existing ones such as: Quartz, calls API to operate tasks, is not humane, and is not friendly enough for distributed support; xxl-job, using jetty communication is not convenient to integrate into the spring framework, and elastic expansion support is not friendly enough Disadvantages such as elastic-job, more dependencies, more troublesome deployment, unfriendly distributed coordination, relatively high learning costs and other shortcomings. [0003] The above-mentioned components are not good enough for distributed support, or cannot be elastically expanded, o...

AI Technical Summary

Problems solved by technology

Existing ones such as: Quartz, calls API to operate tasks, is not humane, and is not friendly enough for distributed support; xxl-job, using jetty communication is not convenient to integrate into the spring framework, and elastic expansion support is not friendly enough Disadvantages such as elastic-job, more dependencies, more troublesome deployment, unfriendly distributed coordination, relatively high learning costs, etc.

[0003] The above-mentioned components are either not good enough for distributed support, or cannot be elastically expanded, or are difficult to deploy, learn to use and costly, etc., which are somewhat inappropriate in some aspects

Images