apache/shardingsphere-elasticjob

Distributed scheduled job

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 8th, 2026
Created on September 11th, 2015
Open Issues & Pull Requests: 117 (+0)
GitHub issues: Enabled
Number of forks: 3,247
Total Stargazers: 8,210 (+0)
Total Subscribers: 612 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 42
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,212 days
Stale 30+ days: 41
Stale 90+ days: 14

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • need more info (30)
  • enhancement (16)
  • bug (15)
  • volunteer wanted (12)
  • need feedback (10)
  • ui (10)
  • kernel (8)
  • question (7)

Detailed Description

ElasticJob is a distributed scheduled job framework that enables elastic scheduling, resource management, and job governance across distributed systems.

The tool addresses the operational complexity of running scheduled tasks at scale. It provides job sharding to distribute work across multiple nodes, automatic failover and recovery when nodes fail, and dynamic resource allocation as the system scales. Developers define jobs once using a unified API and the framework handles deployment, scaling, and high availability automatically. The architecture is lightweight and decentralized, relying on ZooKeeper for coordination rather than a central scheduler.

Teams should adopt ElasticJob when they need scheduled tasks to run reliably across multiple servers with automatic scaling and fault tolerance. It suits applications requiring job sharding for throughput improvement and those where operators need minimal manual intervention for job management. The framework supports multiple job types including dataflow, script, HTTP, and file-based jobs, and integrates with Spring for dependency injection. An admin console provides job administration, event tracing, and registry management capabilities.

The project maintains active development with regular commits addressing bug fixes and feature enhancements. Pull requests receive timely review and feedback from maintainers. The codebase shows consistent attention to test coverage and code quality standards. Community engagement occurs through mailing lists and issue discussions, with maintainers responding to user questions and feature requests. The project demonstrates stability through careful handling of breaking changes and backward compatibility considerations across releases.