Cron Jobs on Multiple Replicas: Running Scheduled Tasks Safely
Why in-process cron fires once per replica, how locks, leader election and platform schedulers coordinate, and how to make jobs safe to run twice.
17 min read
Tag
Why in-process cron fires once per replica, how locks, leader election and platform schedulers coordinate, and how to make jobs safe to run twice.
17 min read
Stop duplicate job execution when a monolith scales out. Compare external schedulers, ShedLock-style DB locks and leader election, with SQL and idempotency patterns.
19 min read
Stop scheduled jobs from running once per replica using advisory locks, ShedLock-style lock tables, or leader election, and make them idempotent.
14 min read
Stop duplicate job execution when a monolith scales out: lease locks, ShedLock, Postgres advisory locks, pg_cron, Kubernetes CronJobs and idempotent design.
18 min read
Stop duplicate cron runs in a scaled monolith: classify job semantics, choose distributed locks or leader election, size leases, and make jobs idempotent.
17 min read
Why cron jobs fire once per replica, how to choose between external triggers, per-run locks and leader election, and why jobs must be idempotent.
14 min read