- Update dependencies to fix CVE
- Support for building with OpenJDK 21
- Accelerate the startup speed of ElasticJob
- Migrate from Junit Vintage to Junit Jupiter
- Job class conflict error caused by empty String
- Possible NPE in LegacyCrashedRunningItemListener
- Possible NPE in InstanceService.getAvailableJobInstances
- Job listeners configured in local configuration were used even if overwrite=false
- Add new job dump method in JobOperateAPI
- Avoid once listener invoke multi times
- Fix itemErrorMessages not cleared after job finished.
- Fix Curator notify thread may be blocked and avoid probably endless loop in ServerService.
- NPE occur when job instance could not be unmarshalled.
- Fix failover too sensitive.
- Script Job exception's stack was ignored.
- Support using different event trace data source when using Spring Boot.
- Supports building project by Java 19.
- Avoids creating too many threads for JobTracingEventBus
- Job listeners can be ordered
- Supports setting timezone for job
- Some enhancements in Spring Boot Starter
- Supports configuring preferred ip by regex
- Lifecycle module: JobOperateAPIImpl#trigger does not work
- Job conflict may occur when using Spring Boot Starter
- Support configuring Mail SMTP SSL trust in elasticjob-error-handler-email
- The failover may not work in distributed deployment
- ReconcileService is still running after the job shutdown
- Make the spring-boot-starter-jdbc optional in ElasticJob Spring Boot Starter
- Simplify usage of injecting OneOffJob when using Spring Boot Starter
- Refactor job tracing configuration to support persistence
- Support reloading JobErrorHandler and ExecutorService when configuration changed
- Add authentication support in Cloud Scheduler
- Fix TracingConfiguration doesn't work when the property overwrite is false
- Fix SnapshotService may be unavailable in specific situation
- Fix some minor problems in Restful module
- Upgrade commons-dbcp to commons-dbcp2 in Cloud Scheduler
- Refactor job listener configuration
- Refactor job error handler configuration
- Refactor job tracing configuration
- Support HTTP job
- Remove spring boot dependencies from job kernel module
- Support email notification when job execute error
- Support wechat notification when job execute error
- Support dingtalk notification when job execute error
- Fix bug of one-off job cannot work with sharding
- Fix bug of table and index name case-insensitive for event trace using database
- Fix bug of dead lock when resharding flag set incorrectly
- Upgrade the minimum supported version of JDK to Java8
- Update Zookeeper to version 3.6.x and curator to version 5.1.0
- Update Google Guava to version 29.0-jre
- Change maven groupId to org.apache.shardingsphere.elasticjob
- Change package name to org.apache.shardingsphere.elasticjob
- Change spring namespace name to http://shardingsphere.apache.org/schema/elasticjob
- New job API, use SPI to customize job type
- Use SPI to introduce configuration strategies
- Split console and UI from job core modules
- Add One-off job executor
- Add Spring Boot Starter for ElasticJob-Lite
- Add more databases support for event trace persist
- User indicate IP address via system environment supported
- Fix bug for executor thread ContextClassLoader is empty with ElasticJob-Cloud
- Fix bug for enable job from web console have no effect
- Shutdown job when application exit
- Fix NPE when failover out-of-order in Curator asynchronized persist
- Get correct job class name when using CGLIB proxy
- ISSUE #373 Cloud can distinguish processing TASK_UNREACHABLE,TASK_UNKNOWN,TASK_DROPPED,TASK_GONE,etc
- ISSUE #367 Massive stacked jobs performed after Cloud restart because disabled job does not stop Ready queue
- ISSUE #382 UI verification error, maximum number of shards should not be verified
- ISSUE #383 UI verification error, minimum number of listening port should not be verified
- ISSUE #29 Console support english
- ISSUE #352 Running elastic-job-cloud-executor locally without mesos environment
- ISSUE #322 Schedule tasks to evaluate resources when considering the use of resources for executor in elastic-job-cloud-scheduler module
- ISSUE #341 Script task configuration in elastic-job-cloud-console is missing execution script
- ISSUE #343 Script task execution script is incorrect in elastic-job-cloud-console module
- ISSUE #345 The status is not displayed correctly when the task is all disabled in elastic-job-lite-console module
- ISSUE #351 Manage background add registry, login credentials bar can not enter ':' in elastic-job-lite-console module
- ISSUE #327 spring namespace supports use xml to config beans
- ISSUE #336 Cloud task submission failure returns error details to framework
- ISSUE #321 elastic-job-lite The namespace is not support / when UI adds the registry
- ISSUE #333 elastic-job-lite Registration center configuration login credentials in the UI implicit display
- ISSUE #334 elastic-job-lite UI can't find conf\auth.properties file on windows platform
- ISSUE #335 elastic-job-lite UI guest account configuration does not work in conf\auth.properties file
- ISSUE #301 Console add guest permission configuration, guest only allows viewing, not allowed to change
- ISSUE #312 Cloud support self-healing
- ISSUE #293 Lite Console datasource configuration adds connection testing capabilities
- ISSUE #296 Cloud operational UI refactoring, consistent with lite style
- ISSUE #302 Failure transfer and task run state monitoring separation
- ISSUE #304 Cloud add associated features with Mesos roles
- ISSUE #316 Lite running task association process ID
- ISSUE #291 elastic-job console failure reason display is not complete
- ISSUE #306 Switch whether to monitor job execution status and task intervals are short may occur when the task cannot continue to run
- ISSUE #310 Create to many sequential nodes after configuration check time error seconds for this machine and registry
- ISSUE #242 Elastic-Job-Cloud supports delete application and task
- ISSUE #243 Elastic-Job-Cloud supports enable/disable application and task
- ISSUE #268 Simplify POM dependency
- ISSUE #266 Elastic-Job-Lite start script specifies that the port is invalid
- ISSUE #269 EventTrace failure record is not affected by sample rate and the time of failure is recorded
- ISSUE #270 Console send two requests after clicks the button
- ISSUE #272 Elastic-Job-Lite UI job dimensions that should appear as disabled only if all servers are disabled
- ISSUE #275 After stopping Zookeeper, restart Zookeeper and the task does not continue
- ISSUE #276 When fail transfer is turned on and the shard task is performed, the task is repeated
- ISSUE #279 Add event tracking data source, database connection address can not have parameters
- ISSUE #280 The historical status of the task history page is not displayed correctly
- ISSUE #283 Task is not set overwrite and local configuration is inconsistent with the registration center, the cron started by the task shall be based on the registry
- ISSUE #290 Elastic-Job-Cloud when deleting a disabled APP or JOB, the corresponding disabled node data cannot be deleted
- ISSUE #195 Elastic-Job-Lite self-diagnose and fix problems caused by distributed instability
- ISSUE #248 Elastic-Job-Lite the same job server can run multiple JVM instances with the same job name(Cloud Native)
- ISSUE #249 Elastic-Job-Lite Operations UI supports incident tracking queries
- ISSUE #240 Elastic-Job-Lite operational UI refactoring.
- ISSUE #262 Elastic-Job-Lite console delete job configuration.
- ISSUE #237 Add the REST API check on the total number of shards not less than 1
- ISSUE #238 IP regular expression error
- ISSUE #246 After using JobOperateAPI.remove()，JobScheduler.init() triggers execution multiple times after creating the same job
- ISSUE #250 Misfire task triggers more than once
- ISSUE #263 Elastic-Job-Lite Job OperationAPI Re-grooming
- ISSUE #264 Elastic-Job-Lite Data storage restructuring, but forward compatibility
- ISSUE #191 Framework's HA feature
- ISSUE #217 cloud add APP dimension configuration
- ISSUE #223 cloud resident job event tracking sample rate
- ISSUE 222 elastic-job-lite-spring reg configuration parameter max-retries does not work
- ISSUE 231 When a cloud job is deleted in bulk, mesos synchronizes TASK_LOST message to the framework in advance, causing the job to be re-arranged in the ready queue and executed
- ISSUE #203 Cloud task add run statistics and provide REST API queries
- ISSUE #215 cloud operations management UI
- ISSUE #187 ShardingContext add task attribute to business side
- ISSUE #189 Manage background to perform a failure operation, but the task is still being executed
- ISSUE #204 Async execution of messages in consistency results in inaccurate database data
- ISSUE #209 cloud task resource allocation algorithm improvement
- ISSUE #184 ExecutorServiceHandler interface method adjustment, add jobName used to distinguish between different job thread names
- ISSUE #186 Simplify SpringJobScheduler use by removing Spring Namespace DTO-related code
- ISSUE #178 Event-driven trigger jobs
- ISSUE #179 Transient's Script-type task optimization, no Java Executor support required
- ISSUE #182 add support for spring boot
- ISSUE #177 Spring Namespace Job: Script Null Pointer in version 2.0.2
- ISSUE #185 Executor over-occupancy of sharding resources leads to waste of resources
- ISSUE #153 Centralization of event tracking configuration
- ISSUE #160 Adjust the maven module structure to provide elastic-job-common and its secondary modules, the original elastic-job-core module migration to elastic-job-common-core
- ISSUE #159 Available in any version from Spring 3.1.0.RELEASE to Spring 4
- ISSUE #164 JobBeans that have been declared in the job Spring namespace no longer need to declare @Component or define in Spring xml
- ISSUE #64 Spring namespace, if you register multiple job beans of the same class, will cause job beans to look up inaccurately
- ISSUE #115 Console add new registry, no connection success, back stage has been repeatedly connected and reported errors
- ISSUE #151 Lack of support for relational database-based event tracking for databases outside MySQL
- ISSUE #152 Job custom exception processor is invalid and is always handled by Default JobExceptionHandler
- ISSUE #156 Job event tracking overall call link data acquisition
- ISSUE #158 Job misses sharding when it is paused and will no longer shard
- ISSUE #161 Version of Lite deployed to some versions of Tomcat cannot be started
- ISSUE #163 The project is started or the task is automatically performed after the task is set to disable true
- ISSUE #165 Shard thread deadlock when all service nodes are disable
- ISSUE #167 Failover job adds task ID record
- ISSUE #141 Remove the reg module to read information from zk, making the reg namespace's placeholder fully available
- ISSUE #143 elastic-job-cloud-scheduler memory leak
- ISSUE #145 After modifying the database connection of the task log, the log is still written to the old database
- ISSUE #146 Thread pool reuse problem for a task
- ISSUE #147 console task does not load, background there is an null pointer exception
- ISSUE #149 Operations platform delete tasks, occasionally encounter deletion incomplete situation
- ISSUE #150 Cloud's misfire feature will be performed as jobs pile up
- Elastic-Job-Cloud initial version
- Reconstruct the original Elastic-Job to Elastic-Job-Lite
- ISSUE #119 Quartz does not close properly when spring container is closed
- ISSUE #123 Stand-alone running timing task, zk disconnect after reconnecting, did not trigger the leader election
- ISSUE #127 Spring configuration task id cannot use placeholders
- ISSUE #116 HandleJobExecutionException parameter changes for job interface
- ISSUE #110 Trigger the task manually
- ISSUE #99 After deleting a task asynchronously caused the job to be deleted, the task that has not yet ended continues to create zk data
- ISSUE #97 JobConfiguration Refactored to SimpleJobConfiguration，DataflowJobConfiguration，ScriptJobConfiguration
- ISSUE #102 Redefine Java/Spring Config API，replace Constructor+Setter with Factory+Builder model
- ISSUE #104 Remove @Deprecated code
- ISSUE #105 Reconstructing the Spring Namespace Hump Definition
- ISSUE #106 isStreaming Configuration
- ISSUE #107 reg-center renamed registry-center-ref
- ISSUE #95 Add script type job support
- ISSUE #88 Stop task renamed pause
- ISSUE #91 Job Lifecycle Action API
- ISSUE #84 The console provides job enable/disable button action
- ISSUE #87 Adjusting the master node election process, job shutdown, disabling and pausing will trigger the master node election
- ISSUE #93 The registry configuration provides default values for baseSleepTimeMilliseconds, maxSleepTimeMilliseconds, and maxRetries
- ISSUE #92 Modifying the total shard parameter results in a listening throw timeout exception performed by only a single node
- ISSUE #71 Task off function（shutdown）
- ISSUE #72 Closed jobs can be deleted
- ISSUE #81 Using the last end state of a centralized cleanup job instead of the respective cleanup, each cleaning may result in an uncleaned end state due to offline
- ISSUE #74 When streaming and fail transfer, the failover shard item cannot be executed once and stopped
- ISSUE #77 Dataflow type task, fetchData if there is data, should be executed in pairs with processData
- ISSUE #78 Spring configuration job monitoring enable AOP causes problems that do not work properly
- ISSUE #59 elastic-job upgrade curator from 2.8.0 to 2.10.0
- ISSUE #2 Add front and post tasks
- ISSUE #60 Dataflow type task customized thread pool configuration
- ISSUE #62 Job status cleanup speed-up
- ISSUE #65 Add spring namespace support for front and post tasks
- ISSUE #61 Deadlock problem solved when sharding and primary node elections occur at the same time
- ISSUE #63 You may get TreeCache for other jobs with the same prefix when you get the job TreeCache
- ISSUE #69 If the job server sharding node in Zk does not exist when sharding, it will not be able to reshard
- ISSUE #57 Thin module, remove elastic-job-test module
- ISSUE #58 Add changes in job type interfaces due to bulk processing capabilities
- ISSUE #16 Provides embedded zookeeper to simplify the development environment
- ISSUE #28 Dataflow type tasks to increase processData bulk processing of data
- ISSUE #56 Job custom parameter settings
- ISSUE #39 Add job assisted listening and fetch job runtime information with dump command
- ISSUE #43 Add job exception handling callback interface
- ISSUE #30 Registry is down for a long time and resumes, and the job cannot continue
- ISSUE #36 Task cannot resume after console pause
- ISSUE #40 TreeCache uses Coarse granularity cause memory overflow
- ISSUE #17 Task type interface changes
- ISSUE #6 Proofreading job server and registry time error
- ISSUE #8 Increase misfire switch, default enable missed task re-execution
- ISSUE #9 Sharding policy configurability
- ISSUE #10 Provides a sorting strategy for odd even shards based on job name hash value
- ISSUE #14 When the console modifies the cron expression, the task updates the cron in real time
- ISSUE #20 Operations UI task list shows increased cron expression
- ISSUE #54 Sequenceperpetual task performance improved, changing fetch data to multithreaded, previously processing data only as multithreaded
- ISSUE #55 offset storage capabilities
- ISSUE #1 Inaccurate access to IP addresses in complex network environments
- ISSUE #13 After a job throws a run-time exception, it does not continue to be triggered later
- ISSUE #53 Dataflow's Sequence type tasks use multithreaded fetch data
- Initial version