-
Notifications
You must be signed in to change notification settings - Fork 92
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
Store job process and queue id #86
Comments
With this information in place, it should be possible to provide a functionality in Cylc to manually or automatically query the status of a task in a queueing system. If a running task is not found in the queueing system where it should be, it should be marked as failed. |
Yes, this would be useful. It would handle nasty external hard-kills that we can currently only handle with timeouts. |
In addition to the queue id and process id we also need to record what system the task was submitted to (noting that the host can be a command so you can't just rely on the suite config) - this info will need to be available after a restart. |
I thought I'd already noted these points:
|
The following ideas were sent to @hjoliver via email originally: Introduce the task information/event log. E.g. For each task job, create an event log file to store common information. E.g.:
It will also have markers to indicate whether a message has been sent to the suite or not. The file has these uses:
E.g.:
A line containing |
#282: Job process ID and submit method ID ( |
@matthewrmshin - can this issue be closed now? I can open new smaller issues for extending this functionality to other job submission methods. |
@hjoliver If you are happy for this to close, please feel free. |
It would be useful to store a job's process and/or queue id in order to query the status of a running job or kill it.
The text was updated successfully, but these errors were encountered: