sibson/redbeat

Redbeat scheduler - Execute same task at same time interval but for different inputs

Open

#93 opened on Jun 12, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (815 stars) (122 forks)batch import
help wanted

Description

We are creating scheduler entry for 3 different ID's using the below code.

interval = schedule(run_every=60) RedBeatSchedulerEntry('{0}'.format(id), 'method_name', interval, kwargs=kwargs, app=app).save()

There are 3 different entries now, all of them with the same time interval to run every 60 seconds Below are the observations: --> Only the first task entry is getting executed every 60 secs --> Other two never get executed --> No exception or error seen for other entries

Excepted behavior : All 3 tasks which were assigned to run every 60 seconds to execute same method should be executed

Contributor guide

Tech stack
pythonredis
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
PythonRedisCelery
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the RedBeatSchedulerEntry.save() method to understand how it stores entries in Redis. The issue suggests that only the first entry with a given interval is executed, implying possible key collision or overwriting. Examine the Redis data structure used (e.g., sorted sets) and the logic for updating schedule entries. Look at the Celery beat scheduler's behavior for multiple tasks with the same interval. Check if there is an existing test case for this scenario.