Sorry,didn’t send to the list Anfang der weitergeleiteten Nachricht:
Von: Henkel <hen...@uni-mainz.de<mailto:hen...@uni-mainz.de>> Datum: 8. August 2019 um 09:21:55 MESZ An: "Sarlo, Jeffrey S" <jsa...@central.uh.edu<mailto:jsa...@central.uh.edu>> Betreff: Aw: [slurm-users] Getting information about AssocGrpCPUMinutesLimit for a job Hi Jeff, Users may call sshare -l and have a look at the TRESRunMin. There the number of TRES-minutes allocated by jobs currently running against the account is listed. With a little math (cpu*timelimit) about the job in question the users should be able to figure this out. At least they wouldn't need the debug level increased ot a log file. Best, Andreas On 8/7/19 8:47 PM, Sarlo, Jeffrey S wrote: We had a job queued waiting for resources and when we changed the debug level, we were able to get the following in the slurmctld.log file. [2019-08-02T10:03:47.347] debug2: JobId=804633 being held, the job is at or exceeds assoc 50(jeff/(null)/(null)) group max tres(cpu) minutes of 30000000 of which 1436396 are still available but request is for 1440000 (plus 0 already in use) tres minutes (request tres count 80) We were then able to see that we just needed to lower the timelimit for the job a little. Is there a way a user can get this same type of information for a job, without having to change the slurm debug level and then looking in a log file? Thanks. Jeff -- Dr. Andreas Henkel Operativer Leiter HPC Zentrum für Datenverarbeitung Johannes Gutenberg Universität Anselm-Franz-von-Bentzelweg 12 55099 Mainz Telefon: +49 6131 39 26434 OpenPGP Fingerprint: FEC6 287B EFF3 7998 A141 03BA E2A9 089F 2D8E F37E
0xE2A9089F2D8EF37E.asc
Description: 0xE2A9089F2D8EF37E.asc
