sibson/redbeat

Documentation Improvement - REDBEAT_LOCK_TIMEOUT

Open

#92 opened on Jun 1, 2018

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

Description

REDBEAT_LOCK_TIMEOUT = CELERYBEAT_MAX_LOOP_INTERVAL * 5 needs to be explicitly set or it defaults to 25 minutes. In production this can cause a hang if the service crashes or has another issue where it does not clean itself up.

Appears to be related to this discussion: #50

Easiest if this were referenced in documents as a suggested config to avoid issues.

Contributor guide

Tech stack
pythonredis
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
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.
clear
Prerequisites
Knowledge of Celery and Redis basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The issue requests adding documentation for REDBEAT LOCK TIMEOUT configuration. The value defaults to CELERYBEAT MAX LOOP INTERVAL * 5 (25 minutes). Refer to discussion #50. To resolve, locate the configuration documentation file in the repository (likely README or docs folder) and add a note suggesting users explicitly set this value to avoid hangs in production. A simple PR adding a sentence about the default and recommendation would suffice.
Documentation Improvement - REDBEAT_LOCK_TIMEOUT · sibson/redbeat#92 | Good First Issue