How do I set up a recurring job with resque-scheduler?

Define the job in a YAML file with cron syntax (e.g., `cron: "0 * * * *"` for hourly), then load it via `Resque.schedule` in your Rake task. You can also specify class, queue, and args in the YAML for customization.

Resque-scheduler vs Sidekiq Cron: which is better for my Rails app?

Choose resque-scheduler if you're already using Resque for background jobs; it integrates seamlessly. Sidekiq Cron is better if you use Sidekiq, as it leverages Sidekiq's threaded model and may offer better performance for high-throughput scenarios.

Can I dynamically add schedules without restarting resque-scheduler?

Yes, but you must enable dynamic scheduling by setting `Resque::Scheduler.dynamic = true` during initialization. Then, use `Resque.set_schedule` to programmatically add or update schedules, which persists if configured.

What happens to delayed jobs if the scheduler crashes?

Delayed jobs are stored in Redis and will be 'caught up' once the scheduler restarts, ensuring they run after their scheduled time, as noted in the documentation. However, missed recurring jobs are not recovered.

How do I remove a specific delayed job in resque-scheduler?

Use `Resque.remove_delayed` with the exact arguments from enqueueing, or `Resque.remove_delayed_selection` for flexible matching based on criteria like user ID, as demonstrated in the README examples.

Is resque-scheduler suitable for jobs that need to run every second?

Not ideally. While it supports six-parameter cron syntax for per-second scheduling, the default polling interval is 5 seconds, so jobs may not fire precisely at the second mark, and high-frequency tasks could face latency.

resque-scheduler — Lightweight Job Scheduling Extension

What is resque-scheduler?

Resque-scheduler is a lightweight job scheduling extension for Resque that allows developers to queue jobs to run at specific times in the future or on a recurring schedule. It solves the problem of handling time-based tasks like sending delayed emails or running periodic maintenance jobs within the Resque ecosystem, eliminating the need for external cron systems.

Target Audience

Ruby developers using Resque for background job processing who need to schedule delayed or recurring tasks, such as sending follow-up emails, generating periodic reports, or performing batch operations at specific times.

Value Proposition

Developers choose Resque-scheduler because it integrates seamlessly with Resque, providing a familiar API and infrastructure for scheduling without introducing new dependencies. Its support for both delayed and recurring jobs, along with features like dynamic scheduling and failover, makes it a robust and flexible solution for time-based job management.

A light-weight job scheduling system built on top of Resque

Use Cases

Best For

Scheduling one-off delayed jobs like sending follow-up emails after a few days
Setting up recurring cron-like jobs for periodic tasks such as data cleanup or report generation
Building applications that require dynamic job scheduling without restarting the scheduler process
Ensuring high availability for scheduled jobs with redundant scheduler instances and failover
Managing time-based tasks within an existing Resque-based background job infrastructure
Replacing external cron systems with an integrated Ruby-based scheduling solution

Not Ideal For

Teams using alternative background job systems like Sidekiq or Active Job without Resque
Applications requiring millisecond-accurate job timing, as resque-scheduler polls at intervals (default 5 seconds)
Projects that need scheduling across polyglot microservices, since it's tightly coupled with Ruby and Resque
Environments where external cron systems are preferred for their simplicity and universal availability

Pros & Cons

Pros

Seamless Resque Integration

Integrates directly with Resque's Redis configuration and API, allowing delayed jobs to be enqueued using familiar methods like `Resque.enqueue_in`, as shown in the basic usage examples.

Flexible Scheduling Modes

Supports both one-off delayed jobs and cron-like recurring jobs via YAML configuration, providing versatility for time-based tasks such as sending emails or running maintenance.

Dynamic Schedule Management

When enabled with `Resque::Scheduler.dynamic = true`, schedules can be added, updated, or removed at runtime without restarting the scheduler process, offering flexibility for changing requirements.

Redundant Scheduler Support

Allows multiple scheduler instances with master election to ensure high availability, preventing single points of failure for scheduled jobs, as detailed in the redundancy section.

Cons

Polling-Induced Latency

Jobs are not executed exactly at the scheduled time; the scheduler polls at intervals (default 5 seconds), meaning there can be delays, as admitted in the delayed jobs section where it states jobs fire after the time has passed.

Setup and Configuration Complexity

Requires careful setup with Rake tasks, environment variables, and optional dynamic scheduling enablement, which can be error-prone for new users, as shown in the installation and configuration examples.

Ecosystem Lock-in

Tightly coupled with Resque and Ruby, making it unsuitable for projects using other job queues or polyglot architectures, and it adds dependencies on Redis and specific gem versions.

Missed Recurring Jobs

If the scheduler process is down, missed scheduled jobs are not recovered upon restart, unlike delayed jobs, which can lead to gaps in periodic tasks, as noted in the redundancy section.

Frequently Asked Questions

What is resque-scheduler?

Target Audience

Value Proposition

Use Cases

Best For

Scheduling one-off delayed jobs like sending follow-up emails after a few days
Setting up recurring cron-like jobs for periodic tasks such as data cleanup or report generation
Building applications that require dynamic job scheduling without restarting the scheduler process
Ensuring high availability for scheduled jobs with redundant scheduler instances and failover
Managing time-based tasks within an existing Resque-based background job infrastructure
Replacing external cron systems with an integrated Ruby-based scheduling solution

Not Ideal For

Teams using alternative background job systems like Sidekiq or Active Job without Resque
Applications requiring millisecond-accurate job timing, as resque-scheduler polls at intervals (default 5 seconds)
Projects that need scheduling across polyglot microservices, since it's tightly coupled with Ruby and Resque
Environments where external cron systems are preferred for their simplicity and universal availability

Pros & Cons

Pros

Seamless Resque Integration

Integrates directly with Resque's Redis configuration and API, allowing delayed jobs to be enqueued using familiar methods like `Resque.enqueue_in`, as shown in the basic usage examples.

Flexible Scheduling Modes

Supports both one-off delayed jobs and cron-like recurring jobs via YAML configuration, providing versatility for time-based tasks such as sending emails or running maintenance.

Dynamic Schedule Management

When enabled with `Resque::Scheduler.dynamic = true`, schedules can be added, updated, or removed at runtime without restarting the scheduler process, offering flexibility for changing requirements.

Redundant Scheduler Support

Allows multiple scheduler instances with master election to ensure high availability, preventing single points of failure for scheduled jobs, as detailed in the redundancy section.

Cons

Polling-Induced Latency

Setup and Configuration Complexity

Ecosystem Lock-in

Tightly coupled with Resque and Ruby, making it unsuitable for projects using other job queues or polyglot architectures, and it adds dependencies on Redis and specific gem versions.

Missed Recurring Jobs

If the scheduler process is down, missed scheduled jobs are not recovered upon restart, unlike delayed jobs, which can lead to gaps in periodic tasks, as noted in the redundancy section.

Frequently Asked Questions

resque-scheduler

What is resque-scheduler?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

resque-scheduler

What is resque-scheduler?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?