<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div dir="ltr"></div>
<div dir="ltr"><br>
Sorry,didn’t send to the list<br>
<br>
Anfang der weitergeleiteten Nachricht:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr"><b>Von:</b> Henkel <<a href="mailto:henkel@uni-mainz.de">henkel@uni-mainz.de</a>><br>
<b>Datum:</b> 8. August 2019 um 09:21:55 MESZ<br>
<b>An:</b> "Sarlo, Jeffrey S" <<a href="mailto:JSarlo@Central.UH.EDU">JSarlo@Central.UH.EDU</a>><br>
<b>Betreff:</b> <b>Aw: [slurm-users] Getting information about AssocGrpCPUMinutesLimit for a job</b><br>
<br>
</div>
</blockquote>
<div dir="ltr"><span></span></div>
<blockquote type="cite">
<div dir="ltr"><span>Hi Jeff,</span><br>
<span></span><br>
<span>Users may call sshare -l and have a look at the TRESRunMin. There the</span><br>
<span>number of TRES-minutes allocated by jobs currently running against</span><br>
<span>the account is listed. With a little math (cpu*timelimit) about the job</span><br>
<span>in question the users should be able to figure this out. At least they</span><br>
<span>wouldn't need the debug level increased ot a log file.</span><br>
<span></span><br>
<span>Best,</span><br>
<span></span><br>
<span>Andreas</span><br>
<span></span><br>
<span>On 8/7/19 8:47 PM, Sarlo, Jeffrey S wrote:</span><br>
<blockquote type="cite"><span>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.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>[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)</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>We were then able to see that we just needed to lower the timelimit for the job a little.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>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?</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Thanks.</span><br>
</blockquote>
<blockquote type="cite"><span>Jeff</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<span>-- </span><br>
<span>Dr. Andreas Henkel</span><br>
<span>Operativer Leiter HPC</span><br>
<span>Zentrum für Datenverarbeitung</span><br>
<span>Johannes Gutenberg Universität</span><br>
<span>Anselm-Franz-von-Bentzelweg 12</span><br>
<span>55099 Mainz</span><br>
<span>Telefon: +49 6131 39 26434</span><br>
<span>OpenPGP Fingerprint: FEC6 287B EFF3</span><br>
<span>7998 A141 03BA E2A9 089F 2D8E F37E</span><br>
<span></span><br>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"></div>
</blockquote>
</body>
</html>