| Summary: | explanation of --endtime | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Vlad Doster <vlad_doster> |
| Component: | User Commands | Assignee: | Albert Gil <albert.gil> |
| Status: | RESOLVED INFOGIVEN | QA Contact: | |
| Severity: | 4 - Minor Issue | ||
| Priority: | --- | ||
| Version: | 18.08.4 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | Harvard Medical School | Alineos Sites: | --- |
| Atos/Eviden Sites: | --- | Confidential Site: | --- |
| Coreweave sites: | --- | Cray Sites: | --- |
| DS9 clusters: | --- | HPCnow Sites: | --- |
| HPE Sites: | --- | IBM Sites: | --- |
| NOAA SIte: | --- | OCF Sites: | --- |
| Recursion Pharma Sites: | --- | SFW Sites: | --- |
| SNIC sites: | --- | Linux Distro: | --- |
| Machine Name: | CLE Version: | ||
| Version Fixed: | Target Release: | --- | |
| DevPrio: | --- | Emory-Cloud Sites: | --- |
|
Description
Vlad Doster
2020-03-18 11:04:49 MDT
Hi Vlad > I am trying to understand --endtime option. > > It seems that when --endtime is passed it only pulls jobs that are in the > RUNNING or PENDING state? It does not mention that in sacct --help so I just > want to make sure that I understand the behavior correctly. Or maybe it is > mentioned somewhere and I overlooked it? First of all let me mention that the behavior, default values and relation between the --starttime, --endtime, --state and --jobs options was fixed in bug 5717 and bug 6697, so the right behavior is available on version 18.08.7 and newer: - https://github.com/SchedMD/slurm/blob/master/NEWS#L847 - https://github.com/SchedMD/slurm/blob/master/NEWS#L804 As it was a confusing we also created an specific DEFAULT TIME WINDOW section in the sacct documentation to explain such relation between options and their default values better: https://slurm.schedmd.com/sacct.html#SECTION_DEFAULT-TIME-WINDOW Probably the main thing to understand is that --starttime and --endtime are NOT related to the times where a job was started or ended to run, but actually they are the way to define a time-window to filter/query jobs that were into a specific --state on that time window. And that, by default, the --state shows jobs in "Eligible" state, ie. that can be scheduled to run or already running (without dependencies or with a --begin time in the future). Take a look to SECTION DEFAULT TIME WINDOW section and please let me know if you have any questions. Also, maybe taking a look into bug 8234 that was also a related questions may help you. And finally, as you know version 20.02 is already released, we encourage you to upgrade to at least the last 19.05 version in order to get proper support, and better Slurm. Regards, Albert |