Hello, Could I please follow up on the Slurm patch that relates to smaller jobs pushing large jobs back? My colleague downloaded and installed the most recent production version of Slurm today and tells me that it did not appear to resolve the issue. Just to note, we are currently running v19.05.8 and finding that the backfill mechanism pushes large jobs back. In theory, should the latest Slurm help us in sorting that issue out? I understand that we're testing v20.11.2, however I should clarify that with my colleague tomorrow.
Does anyone have any comments, please? Is there any parameter that we need to set to activate the backfill patch, for example? Best regards, David ________________________________ From: slurm-users <slurm-users-boun...@lists.schedmd.com> on behalf of Chris Samuel <ch...@csamuel.org> Sent: 09 December 2020 16:37 To: slurm-users@lists.schedmd.com <slurm-users@lists.schedmd.com> Subject: Re: [slurm-users] Backfill pushing jobs back CAUTION: This e-mail originated outside the University of Southampton. Hi David, On 9/12/20 3:35 am, David Baker wrote: > We see the following issue with smaller jobs pushing back large jobs. We > are using slurm 19.05.8 so not sure if this is patched in newer releases. This sounds like a problem that we had at NERSC (small jobs pushing back multi-thousand node jobs), and we carried a local patch for which Doug managed to get upstreamed in 20.02.x (I think it landed in 20.02.3, but 20.02.6 is the current version). Hope this helps! Chris -- Chris Samuel : https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csamuel.org%2F&data=04%7C01%7Cd.j.baker%40soton.ac.uk%7Ccc84ff45cb604a29dd6208d89c614721%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637431288909999119%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OuSpfkTGBscxqTfJ0CbvX44GanHn4J76p9tV1M1AqSw%3D&reserved=0 : Berkeley, CA, USA
