XXL-JOB v2.1.2 release, distributed task scheduling platform

v2.1.2 Release Notes

• 1, task support method: the original class based on the task of developing JobHandler mode, optimized to support the task of developing a method based mode; therefore, the development of a single class may support a plurality of tasks method, multiplexes class

@XxlJob("demoJobHandler")
public ReturnT<String> execute(String param) {
    XxlJobLogger.log("hello world");
    return ReturnT.SUCCESS;
}

• 2, removal of commons-exec, using the native manner, the third party dependent reduction;
• 3, the actuator fixes garbled callback;
• 4, the control center dispatcher servlet loading sequence optimization;
• 5, the actuator callback address https compatible support;
• 6, dependent on a number of projects to upgrade to a newer stable version;
• Note: The latest version of "XxlJobSpringExecutor" logic to adjust the historical project of the component configuration refer to Sample adjust the sample project, with particular attention init and destroy methods need to remove components;

Brief introduction

XXL-JOB is a lightweight distributed task scheduling platform, its core design goal is to develop rapid, simple to learn, lightweight, easy to expand. Open source and now online companies access to the product line, out of the box.

characteristic

• 1, simple: support for CRUD operations tasks through the Web page, simple operation, one minute to get started;
• 2, dynamic: support dynamic modification of the task status, start / stop tasks, and terminates the mandate with immediate effect;
• 3, the dispatch center HA (centric): dispatch center design using "control center" Quartz-based clustering and cluster-implemented deployment, dispatch center can guarantee the HA;
• 4, the actuator HA (distributed): distributed task execution, the task "actuator" supports cluster deployment, can guarantee task execution HA;
• 5, the registry: Actuator periodically automatically registered task, the dispatch center will be registered automatically find and trigger the execution of the task. It also supports manual entry actuators address;
• 6, the elastic expansion volume reduction: Once a new line or offline actuators on the machine, the task will reassign the next scheduling;
• 7, routing strategy: provide rich routing policy cluster deployment actuator comprising: first, last, polling, random, consistency HASH, most do not often use, least recently used failover, busy transfer, etc. ;
• 8, failover: Routing Policy Task select "failover" case, the actuator if one of the machines in the cluster fails, it will automatically switch to a normal Failover actuator transmits a scheduling request.
• 9, the blocking processing policy: when the scheduling processing strategy is too late to perform processing too dense, strategies include: single serial (default), discard subsequent scheduling, scheduling before overwriting;
• 10, the task timeout control: support custom task timeout, the task will take the initiative to run a timeout interrupt tasks;
• 11, the task failure retry: support custom failure retry task, when the task will fail according to a preset failure retry active retry; wherein the support slice task failed retry fragment size;
• 12, the mission fails alarm; the default mail failed to provide warning, while reserve expansion interface can extend messaging aspects, nails and other alarm mode;
• 13, fragmented broadcasting task: when a cluster deployment actuator, select the next task routing policy "fragmented broadcasting" situation, a task scheduler will trigger a cluster broadcast all actuators to perform a task, according to the fragment parameters developed slice task ;
• 14, the dynamic fragmentation: fragmentation broadcasting task to the actuator as a dimension fragmentation, supports dynamic expansion actuator cluster dynamically increasing the number of fragments, collaborative business processes; large volume of data traffic operation is performed to significantly improve tasking capacity and speed.
• 15, event triggers: In addition to "Cron way" and "task-dependent manner" trigger mandate, to support event-based trigger mode task. Dispatch centers provide services API to perform a single task is triggered, the trigger can be flexibly according to business events.
• 16, task progress monitoring: real-time monitoring of the progress of the task;
• 17, Rolling real-time log: support online viewing scheduling results, and support for real-time viewing mode Rolling actuator output complete execution log;
• 18, GLUE: providing Web IDE, support online development tasks logic code, dynamic publishing, real-time compiler into force, the deployment process is omitted on the line. It supports 30 versions of historical versions back.
• 19, Script task: supporting the development of GLUE mode and run a script task, including Shell, Python, NodeJS, PHP, PowerShell and other types of scripts;
• 20, the command line tasks: providing universal primary command-line task Handler (Bean task, "CommandJobHandler"); business only needs to provide command lines;
• 21, task dependencies: Support Configuration sub-task dependencies, when the parent task execution and after the end of the successful implementation of the initiative will trigger the execution of a sub-task, multiple sub-tasks, separated by commas;
• 22, consistency: "control center" to ensure the consistency of the cluster distributed scheduling by DB lock, a task scheduler triggers only one execution;
• 23, custom task parameters: task scheduling supports online configuration parameters into immediate effect;
• 24, the thread pool scheduling: scheduling system triggered scheduling multiple threads running, ensure accurate implementation of scheduling, not blocked;
• 25, data encryption: communication between the control center and the actuator for data encryption, scheduling information to enhance security;
• 26, e-mail alarm: Support mission failure alarm messages, support for configuring multiple e-mail addresses bulk alarm messages;
• 27, push maven central warehouse: the latest stable version will be pushed to the maven central repository, user-friendly access and use;
• 28, run the report: view real-time performance data, such as the number of tasks, scheduling times, number of actuators; and schedule reports, such as the dispatch date maps, maps and other scheduling success;
• 29, all asynchronous: task scheduling process to achieve full asynchronous design, such as asynchronous scheduling, asynchronous operation, such as an asynchronous callback, effective scheduling of intensive traffic clipping, in theory, support the long-running tasks arbitrary;
• 30, cross-platform: providing universal primary task HTTP Handler (Bean task, "HttpJobHandler"); business only needs to provide HTTP link, does not limit the language, platform;
• 31, international: the dispatch center to support international settings, providing Chinese and English language optional, defaults to Chinese;
• 32, of the container: official docker mirror, and updated in real time push dockerhub, further achieve the product out of the box;