[X] I have checked that my issue does not already have a solution in the FAQ
[X] I have searched the existing issues and didn't find my bug already reported there
[X] I have checked that my bug is still present in the latest release
Version
master
What happened?
JOB_1 is started multiple times simultaneously
Logs:
INFO: Started server process [4416]
INFO: Waiting for application startup.
LIFESPAN EVENT
INFO: Application startup complete.
INFO: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
2024-01-02 16:23:18.881490 JOB EXECUTE START
2024-01-02 16:23:18.884502 JOB EXECUTE START
2024-01-02 16:23:18.886518 JOB EXECUTE START
2024-01-02 16:32:20.371804 JOB EXECUTE START
2024-01-02 16:32:20.373802 JOB EXECUTE START
2024-01-02 16:32:20.375804 JOB EXECUTE START
2024-01-02 16:32:20.376797 JOB EXECUTE START
2024-01-02 16:38:18.878416 JOB EXECUTE END
2024-01-02 16:38:18.879395 JOB EXECUTE END
2024-01-02 16:38:18.880385 JOB EXECUTE END
2024-01-02 16:42:20.370167 JOB EXECUTE START
2024-01-02 16:42:20.372169 JOB EXECUTE START
2024-01-02 16:47:20.389294 JOB EXECUTE END
2024-01-02 16:47:20.390294 JOB EXECUTE END
2024-01-02 16:47:20.390294 JOB EXECUTE END
2024-01-02 16:47:20.391297 JOB EXECUTE END
In the logs we can see that 3 same jobs started at "2024-01-02 16:23:18" and started three times again at "2024-01-02 16:32:20"
So how we can restrict starting new jobs if others haven't ended?
And how we can restrict starting more than one the same job at one time for one server?
Things to check first
[X] I have checked that my issue does not already have a solution in the FAQ
[X] I have searched the existing issues and didn't find my bug already reported there
[X] I have checked that my bug is still present in the latest release
Version
master
What happened?
JOB_1 is started multiple times simultaneously
Logs:
In the logs we can see that 3 same jobs started at "2024-01-02 16:23:18" and started three times again at "2024-01-02 16:32:20" So how we can restrict starting new jobs if others haven't ended? And how we can restrict starting more than one the same job at one time for one server?
How can we reproduce the bug?
Code:
jobs db table rows at the startup:
I dont know why in jobs table three of same jobs, maybe because I shutdown the server before jobs executions ended