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
When scheduled/asynchronous jobs are terminated using kill -9 on the daemon host, the daemon should ensure all_jobs/all_scheduled_jobs is also getting updated with an error message in the database tables to identify stale jobs. Ideally all terminated sessions should log errors in the table such that it can help identify the failed jobs during such an unexpected events.
I see the similar behavior in the scenarios when the daemon server is terminated or a daemon pid is terminated as well.
currently, "failure" column in all_jobs/all_scheduled_jobs is empty after being terminated. Is it by design or a bug?
The text was updated successfully, but these errors were encountered:
When scheduled/asynchronous jobs are terminated using kill -9 on the daemon host, the daemon should ensure all_jobs/all_scheduled_jobs is also getting updated with an error message in the database tables to identify stale jobs. Ideally all terminated sessions should log errors in the table such that it can help identify the failed jobs during such an unexpected events.
I see the similar behavior in the scenarios when the daemon server is terminated or a daemon pid is terminated as well.
currently, "failure" column in all_jobs/all_scheduled_jobs is empty after being terminated. Is it by design or a bug?
The text was updated successfully, but these errors were encountered: