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

Lock already taken - skipping run #257

Closed
ilmoi opened this issue Mar 2, 2021 · 1 comment
Closed

Lock already taken - skipping run #257

ilmoi opened this issue Mar 2, 2021 · 1 comment

Comments

@ilmoi
Copy link

ilmoi commented Mar 2, 2021

I'm new to rq-scheduler so pardon if this is a stupid question.

Recently when looking through my app's logs I've started seeing this:

scheduler_1 | 10:48:05 Lock already taken - skipping run

I have rq scheduler running in a Docker container as part of a bigger docker-compose app. I have 1 scheduler and some 15 workers, + Redis to record jobs.

What exactly does the above line mean? Did I somehow end up with more than 1 scheduler process? I seem to never have had more than one scheduler container running (I checked).

@ilmoi
Copy link
Author

ilmoi commented Mar 2, 2021

My bad, I really should have read the docs better. For anyone coming across this in the future the answer is here and here.

Amazing system btw, really re-assuring to know that's how multiple schedulers work!

@ilmoi ilmoi closed this as completed Mar 2, 2021
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