Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RedBeatScheduler does not receive lock_timeout from app config #58

Closed
concreted opened this issue Jun 16, 2017 · 0 comments
Closed

RedBeatScheduler does not receive lock_timeout from app config #58

concreted opened this issue Jun 16, 2017 · 0 comments

Comments

@concreted
Copy link
Contributor

concreted commented Jun 16, 2017

After updating exampleconf.py to include:

REDBEAT_LOCK_TIMEOUT = 15

Running PYTHONPATH=. celery beat --config exampleconf still shows the default lock_timeout:

(.venv) Arics-MacBook-Pro:redbeat aric$ PYTHONPATH=. celery beat --config exampleconf
celery beat v4.0.2 (latentcall) is starting.
__    -    ... __   -        _
LocalTime -> 2017-06-16 12:04:19
Configuration ->
    . broker -> redis://localhost:6379//
    . loader -> celery.loaders.default.Loader
    . scheduler -> redbeat.schedulers.RedBeatScheduler
       . redis -> redis://
       . lock -> `redbeat::lock` 25.00 minutes (1500s)
    . logfile -> [stderr]@%WARNING
    . maxinterval -> 5.00 seconds (5s)

Checking the redbeat::lock key in Redis, it shows a TTL of 1500s rather than 15.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant