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
Job scheduler does not use transactions correctly, and this can lead to deadlocks.
In particular, the query to find schedules to run does not use transaction; yet the updates
to schedules are done under txn. This can lead to a stuck process if the transaction retries
after any changes have been made to any of the schedules.
In addition, currently, a single schedule with any sort of error (planning, etc) would lead to the
entire scheduler loop to be undone.
The text was updated successfully, but these errors were encountered:
Job scheduler does not use transactions correctly, and this can lead to deadlocks.
In particular, the query to find schedules to run does not use transaction; yet the updates
to schedules are done under txn. This can lead to a stuck process if the transaction retries
after any changes have been made to any of the schedules.
In addition, currently, a single schedule with any sort of error (planning, etc) would lead to the
entire scheduler loop to be undone.
The text was updated successfully, but these errors were encountered: