Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error not logging upon termination #11

Open
rsabankar opened this issue Apr 4, 2023 · 0 comments
Open

Error not logging upon termination #11

rsabankar opened this issue Apr 4, 2023 · 0 comments

Comments

@rsabankar
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant