-
Notifications
You must be signed in to change notification settings - Fork 519
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
Missing the runs sometimes. #1625
Comments
@lukas-krecan Please check this |
I have tried the debug guide but no help so far.
|
Sorry, if you are not able to configure logging, I will not be able to help you |
This issue looks similar #1611 (comment) |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
My app is running on 20 machines, and I want scheduler to be executed once in every 5 minutes in any 1 machine by using shedlock.
Scheduler:
Config:
pom.xml
Expected behavior
It should run at-least once every 5 mins without any run miss.
Actual behavior
I am seeing sometimes scheduler is missing the runs, for instance it runs at 12:25, 12:30 and then runs at 12:45, missed 2 runs here. Actual task completes in around (400ms - 3s), thus I have setup 1m and 4m as lockAtLeastFor and lockAtMostFor. config seems correct to me.
Doesn't know what's failing here exactly. As per official docs this can run more than once(which is fine for my use-case) but should never miss the runs.
grafana of tracking the runs (you can clearly see it has missed runs many times).
Stack Reference : https://stackoverflow.com/questions/77566840/shedlock-skipped-runs
The text was updated successfully, but these errors were encountered: