sibson/redbeat

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

Open

#93 创建于 2018年6月12日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Python (815 star) (122 fork)batch import
help wanted

描述

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

贡献者指南

技术栈
pythonredis
领域
backend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
PythonRedisCelery
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
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.