As mentioned in the meeting today, we're experiencing that if we have some sort of sql downtime without warning on the mssql server we're running on, it causes the scheduler to freeze, and we can't isolate the error type or exact cause. Below is an example of how it might look the next day after a scheduler freezes.
We can't recreate the issue, but we've experienced various type of sql errors (shutdown, timeout etc.) in the night time which freezes the scheduler. Manually creating a mssql server, and triggering a shutdown doesn't seem to cause the issue. So i'm just creating this issue, and leaving it open so we can continue to locate the issue, and perhaps some other people will experience it as well.
Maybe it's solvable just by adding a retry connection function in the scheduler, however we've tried implementing a fix into our own scheduler without luck.
Update: We had an issue again last night. It froze mid process, but still updated the sql server as if running (online)
As mentioned in the meeting today, we're experiencing that if we have some sort of sql downtime without warning on the mssql server we're running on, it causes the scheduler to freeze, and we can't isolate the error type or exact cause. Below is an example of how it might look the next day after a scheduler freezes.
We can't recreate the issue, but we've experienced various type of sql errors (shutdown, timeout etc.) in the night time which freezes the scheduler. Manually creating a mssql server, and triggering a shutdown doesn't seem to cause the issue. So i'm just creating this issue, and leaving it open so we can continue to locate the issue, and perhaps some other people will experience it as well.
Maybe it's solvable just by adding a retry connection function in the scheduler, however we've tried implementing a fix into our own scheduler without luck.
Update: We had an issue again last night. It froze mid process, but still updated the sql server as if running (online)