Closed nrathaus closed 6 days ago
I don't think this bug is related to python 3.11, as I am able to recreate this also on 3.10.12
I think the issue is related to acquired_until
value getting "freed"
The value of 30
seems to arrive from self.lock_expiration_delay
Do jobs need to finish within 30 seconds?
This is a known issue (acquired_until isn't refreshed) and should be resolved in the next alpha release.
I'm making an application in Django, I used apscheduler, there are two types of methods that I add to the scheduler: copying files and collecting data from these files; if I add copying files to the scheduler, the scheduler works as it should; if I also add analysis, for example, these two tasks every hour, then the execution of these methods is duplicated, reaching 10 identical tasks, coalesce=True - Does not help Please, help me.
I'm making an application in Django, I used apscheduler, there are two types of methods that I add to the scheduler: copying files and collecting data from these files; if I add copying files to the scheduler, the scheduler works as it should; if I also add analysis, for example, these two tasks every hour, then the execution of these methods is duplicated, reaching 10 identical tasks, coalesce=True - Does not help Please, help me.
If you feel that your issue is separate from this, I think you should create a new ticket with instructions on how to reproduce (without Django).
Right, I haven't actually fixed this quite yet, but laid the groundwork for the fix. I'll close this again when the real fix is in place.
https://github.com/agronholm/apscheduler/issues/864#issuecomment-2105663654 thanks for the reply, the problem was not apscheduler, sorry for the inconvenience, the problem was with the server apache2 had to be run in deamon mode.
I've just pushed a commit which should eliminate the problem of other schedulers acquiring or cleaning up schedules or jobs belonging to a running scheduler.
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
4.0.0a4
What happened?
There seems to be a major bug causing tasks (scheduled) to run more than they are scheduled, in my example one should run every 1 second, and the other once a day, after about 30seconds (I am not sure what this number caused by), the once a day task is launched (again)
Expected
Viewed Outcome
How can we reproduce the bug?