Hello,
Bjørn-Helge Mevik writes:
>> A solution was suggested in
>> https://serverfault.com/questions/1090689/how-can-i-set-up-interactive-job-only-or-batch-job-only-partition-on-a-slurm-clu
>>> Interactive jobs have no script and job_desc.script will be empty /
>> not set.
>>
>> So maybe
Ole Holm Nielsen writes:
> On 5/8/23 08:39, Bjørn-Helge Mevik wrote:
>> Angel de Vicente writes:
>>
>>> But one possible way to something similar is to have a partition only
>>> for interactive jobs and a different partition for batch jobs, and then
>>> enforce that each job uses the right
On 5/8/23 08:39, Bjørn-Helge Mevik wrote:
Angel de Vicente writes:
But one possible way to something similar is to have a partition only
for interactive jobs and a different partition for batch jobs, and then
enforce that each job uses the right partition. In order to do this, I
think we can
Hi,
Bjørn-Helge Mevik writes:
> Wouldn't it be simpler to just refuse too long interactive jobs in
> job_submit.lua?
Yes, I guess. I proposed the idea of having different partitions because
then the constraints are at the level of the partition, which is
probably easier to handle than
Angel de Vicente writes:
> But one possible way to something similar is to have a partition only
> for interactive jobs and a different partition for batch jobs, and then
> enforce that each job uses the right partition. In order to do this, I
> think we can use the Lua contrib module (check the
Hi Marko,
Marko Markoc writes:
> Quick question. Is there a way to limit the runtime on a partition
> only for salloc ? I would like for batch jobs to have a default max
> runtime of the partition but interactive jobs to have shortened
> allowed runtime.
I'm also interested in this (in my case
Hi All,
Quick question. Is there a way to limit the runtime on a partition only for
salloc ? I would like for batch jobs to have a default max runtime of the
partition but interactive jobs to have shortened allowed runtime.
Thanks!
