sibson/redbeat

Support for Celery 4+ sentinel:// urls

Open

#199 opened on Apr 1, 2021

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

Description

Celery 4+ natively supports a different format for specifying redis sentinel instances than the separate celery-redis-sentinel package. It would be helpful if redbeat also supported the native broker url format as well.

Contributor guide

Tech stack
pythonredis
Domain
backend
Issue type
feature
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.
1-3 hours
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.
mostly clear
Prerequisites
Basic knowledge of CeleryRedis familiarityPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how redbeat currently parses broker URLs (likely in redbeat/schedulers.py or similar). Study Celery 4+ documentation for sentinel URL format (redis+sentinel://...). Modify the URL parsing logic to support both the legacy format (via celery redis sentinel package) and the new native format. Ensure backward compatibility with existing configuration. The issue may require updating the backend's Redis connection handling. Consider looking at the one comment for any additional guidance.
Support for Celery 4+ sentinel:// urls · sibson/redbeat#199 | Good First Issue