Hi, My problem is still here, I can't find where is my problem, somebody can help me ?
Thanks Antoine chauvin On 08/08/2013 15:57, Chauvin Antoine wrote: > Hi, > I have some problem with the QOS in SLURM. > I created a user "chauvin" like this: > > /sacctmgr create user chauvin Account=sr Cluster=isei > DefaultAccount=sr defaultqos=parallel > qoslevel=normal,mononode,parallel,urgent,heavy,serial > Fairshare=parent AdminLevel=none// > > / > > /And I have in my configuration /7 QOS with one named "runnow" that > give a plus 10000 priority to the job. It is to be used only by admin. > > +----+----------+ > | id | name | > +----+----------+ > | 1 | normal | > | 3 | mononode | > | 5 | serial | > | 6 | parallel | > | 7 | urgent | > | 8 | runnow | > | 9 | heavy | > +----+----------+ > > This user "chauvin" should not be allowed to use this "runnow" qos. > But when I try to do it, the job is created with this QOS. > I can see the status "Reason Waiting InvalidQOS" for this job, but > also the plus 10000 priority. > > /JOBID USER PRIORITY AGE FAIRSHARE PARTITION > QOS// > //4063 chauvin 1000 1 0 > 1000 0// > //4064 chauvin 1000 1 0 > 1000 0// > //4065 chauvin 11000 1 0 > 1000 10000// <-- The job with runnow priority > > / > > Am i doing something wrong ? Or is this something abnormal ? > > Thanks > > > > > -- > > ---------------------------------------------- > Antoine CHAUVIN > Groupe SR > Synchrotron SOLEIL > 01 69 35 93 23 > -- ---------------------------------------------- Antoine CHAUVIN Groupe SR Synchrotron SOLEIL 01 69 35 93 23
