sibson/redbeat

Documentation Improvement - REDBEAT_LOCK_TIMEOUT

Open

#92 创建于 2018年6月1日

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

描述

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.

贡献者指南

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