ShardingSphere ElasticJob Cloud Scheduler
ShardingSphere ElasticJob Cloud Scheduler is a distributed job scheduling system for self-hosted infrastructure that runs scheduled or triggered tasks across…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
38/100 Low
- Maintained
- 0GitHub repository is archived
- Popular
- 788,197 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 79no serious findings, 1 minor, tests
Based on 4 of 5 factors.
- GitHub stars
- 8,197
- Open issues
- 113
- Last commit
- 2026-10-27
- Latest release
- 3.0.5
- License
- Apache-2.0
- Activity
- steady
Checked 12 days ago - source: GitHub (apache/shardingsphere-elasticjob)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Pick a free Proxy port and config folder When starting ShardingSphere-Proxy (the service that talks to your databases), you can pass a network port (the connection number it listens on) and a config folder to start.sh. This keeps the service from failing on a busy port or reading the wrong settings. source
- Start Proxy from its main folder Run sh bin/start.sh from the ShardingSphere-Proxy directory so the start script can find its files. Starting from the wrong folder can make the service fail to start. source
- Open port 8123 for optional ClickHouse If you enable the optional ClickHouse plugin, you can start ClickHouse with Docker Compose (a file that launches containers) and open port 8123. That port is how other tools connect to the ClickHouse server. source
- Current repository The cloud repo was transferred; use apache/shardingsphere-elasticjob for current source and docs. source
Fetched 14 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Where should I look for the ShardingSphere-ElasticJob-Cloud-Scheduler repository?
The separate Cloud Scheduler repository has been transferred to the main ShardingSphere-ElasticJob repository.
Does ElasticJob include Java 19 compatibility in its recent updates?
Community update notes mention Java 19 compatibility among recent ElasticJob improvements.
What Cloud Scheduler startup symptom is listed in the ElasticJob FAQ?
Cloud Scheduler can fail to start and keep logging that a node’s IP and port has leadership.
Answers sourced from github.com, shardingsphere.apache.org, www.reddit.com
Community
Collected 49 days ago - public community threads