You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usage:
I'm Using apscheduler with django-apscheduler's DjangoJobStore, got error "MySQL server has gone away" when the job's interval is very long.
here's package's version:
django-apscheduler==0.5.2
shellescape==3.8.1
I have read previous issues about my problem, and i came out an thought, could it possible to add a new listener named
"EVENT_JOBSTORE_GET_ERROR", which is used to notify user when "getting job from job store" stage raised an exception.
Then user add a listener to handle this error. In my case, i would recreate an conncetion to mysql and retry.
please, tell me it this gonna work?
The text was updated successfully, but these errors were encountered:
The current game plan for APScheduler 4.0 is to encapsulate reconnection logic in the data store itself, so the scheduler does not have to care. Only unrecoverable errors should fall through which would then crash the entire scheduler. That said, I'm not opposed to the idea of the data store sending events when it has trouble with the underlying service.
Usage:
I'm Using apscheduler with django-apscheduler's DjangoJobStore, got error "MySQL server has gone away" when the job's interval is very long.
here's package's version:
I have read previous issues about my problem, and i came out an thought, could it possible to add a new listener named
"EVENT_JOBSTORE_GET_ERROR", which is used to notify user when "getting job from job store" stage raised an exception.
Then user add a listener to handle this error. In my case, i would recreate an conncetion to mysql and retry.
please, tell me it this gonna work?
The text was updated successfully, but these errors were encountered: