On 2016-01-29 16:45, David Roman wrote:
> Hi, 
> 
> With "FastSchedule=1" in two cases, the second job wait the end of the first 
> job.
> But in my script I need to remove the parameter : #SBATCH --mem=2048 else I 
> have this error 
> 
> sbatch: error: Memory specification can not be satisfied
> sbatch: error: Batch job submission failed: Requested node configuration is 
> not available

Makes sense
http://slurm.schedmd.com/cons_res.html
"
In the cases where Memory is the consumable resource or one of the two
consumable resources the RealMemory parameter, which defines a node's
amount of real memory in slurm.conf, must be set when FastSchedule=1.
"
So, you can avoid setting RealMemory with fastschedule=0
but then -- as I posted earlier:

FastSchedule
0
    Base scheduling decisions upon the actual configuration of each
individual node except that the node's processor count in Slurm's
configuration must match the actual hardware configuration if
PreemptMode=suspend,gang or SelectType=select/cons_res are configured
(both of those plugins maintain resource allocation information using
bitmaps for the cores in the system and must remain static, while the
node's memory and disk space can be established later).

(And you are using PreemptMode=suspend,gang...)

And you didn't /proof/ your actual configuration -- not to discredit
you, but I know how often I failed myself to actually show and _not just
assume_.

/Benjamin

> 
> 
> I try the other solutions that you give me, and I tell you what happens.
> 
> PS : I'm sorry, but my English is not very good.
> 
> David
> 
> 
> -----Message d'origine-----
> De : Benjamin Redling [mailto:[email protected]] 
> Envoyé : vendredi 29 janvier 2016 15:32
> À : slurm-dev <[email protected]>
> Objet : [slurm-dev] Re: Ressouces allocation problem
> 
> 
> 
> 
> Am 29.01.2016 um 15:08 schrieb David Roman:
>> I created 2 jobs
>> Job_A uses 8 CPUS in partion DEV
>> Job_B uses 16 CPUS in partion LOW
>>
>> If I start Job_A before Job_B, all is ok. Job_A is in RUNNING state 
>> and Job_B is in PENDING state
>>
>> BUT, If I start Job_B before Job_A. The both jobs are in RUNNING state.
> 
> [...]
> 
>> FastSchedule=0
> 
> Can you set this to "1"?
> 
> What ever you post about your partitions resource configuration, it is not 
> taken into considerations.
> I think I could construct a case very your behaviour is fine considering your 
> _actual configuration_ and not your _configured resources_
> 
> https://computing.llnl.gov/linux/slurm/slurm.conf.html
> There section *FastSchedule*
> <--- %< --->
> 0
>     Base scheduling decisions upon the actual configuration of each 
> individual node except that the node's processor count in SLURM's 
> configuration must match the actual hardware configuration if 
> SchedulerType=sched/gang or SelectType=select/cons_res are configured (both 
> of those plugins maintain resource allocation information using bitmaps for 
> the cores in the system and must remain static, while the node's memory and 
> disk space can be established later).
> <--- %< --->
> 
> Regards, Benjamin
> --
> FSU Jena | JULIELab.de/Staff/Benjamin+Redling.html
> vox: +49 3641 9 44323 | fax: +49 3641 9 44321
> 


-- 
FSU Jena | JULIELab.de/Staff/Benjamin+Redling.html
vox: +49 3641 9 44323 | fax: +49 3641 9 44321

Reply via email to