There are two ways to confirm your PriorityWeightAge setting has been read in:

$ scontrol show conf | grep PriorityWeightAge
or
$ sprio -w

Once you confirm that the system has recognized the values you set in your 
slurm.conf file, if you still see the problem, I suggest you turn up debugging 
and set the following in your slurm.conf file:

DebugFlags=Priority
SlurmctldDebug=debug5

and see what your slurmctld.log tells you.

Don

From: yogendra.shar...@wipro.com [mailto:yogendra.shar...@wipro.com]
Sent: Monday, November 11, 2013 10:25 PM
To: slurm-dev
Cc: mini...@gmail.com
Subject: [slurm-dev] Re: Slurm configuration problem --Age factor not working @ 
all


Hi All,





Plz help me with below issue. Is this a bug in slurm-2.6.2 because of which age 
factor is not contributing to job priority even little. We have set up 
everything fine (we believe).





--

Regards,

Yogendra

________________________________
From: Yogendra Kumar Sharma (WI01 - GIS - ENU)
Sent: Monday, November 11, 2013 4:35 PM
To: slurm-dev
Cc: Pankaj Sharma (WI01 - GIS); mini...@gmail.com
Subject: RE: [slurm-dev] Re: Slurm configuration problem --Age factor not 
working @ all

Dear Carles,



Please find attachement of slurm.conf.

PriorityMaxAge=10 is already set.

Pls let me know if I am missing any other thing.



Regards,



Yogendra



________________________________
From: Carlos Fenoy [mini...@gmail.com]
Sent: Monday, November 11, 2013 3:52 PM
To: slurm-dev
Cc: Pankaj Sharma (WI01 - GIS)
Subject: [slurm-dev] Re: Slurm configuration problem --Age factor not working @ 
all
Dear Yogendra,
It seems you are missing the PriorityMaxAge parameter.
Set it and the Age parameter should start working.

Regards,
Carles Fenoy

On Mon, Nov 11, 2013 at 11:04 AM, 
<yogendra.shar...@wipro.com<mailto:yogendra.shar...@wipro.com>> wrote:

Hi Team





We have enabled mutlifactor priority (PrirityWeightAge & PriorityJobSize) but 
PrirityWeightAge is not working, our jobs are always scheduled based on 
Jobsize, when we see sprio -l it always show job age = 0. Below are the 
priorities which we have configured and we are using slurm 2.6.2, For testing 
we are submitting sleep jobs i  minutes.



Please help me enabling  Age factor also in our configuration.



[root@hpca ~]# sprio  -l
  JOBID     USER   PRIORITY   AGE  FAIRSHARE    JOBSIZE  PARTITION        QOS   
NICE
    102     root        968          0          0        469        500         
 0      0
    103     root        968          0          0        469        500         
 0      0
    104     root        968          0          0        469        500         
 0      0

 Below is the part of my slurm.conf

----------------------------------------------------

# TIMERS
#BatchStartTimeout=10
#CompleteWait=0
#EpilogMsgTime=2000
#GetEnvTimeout=2
#HealthCheckInterval=0
#HealthCheckProgram=
InactiveLimit=0
KillWait=10
#MessageTimeout=10
#ResvOverRun=0
MinJobAge=2
#OverTimeLimit=5
SlurmctldTimeout=120
SlurmdTimeout=300
#UnkillableStepTimeout=60
#VSizeFactor=0
Waittime=0
#
#
# SCHEDULING
#DefMemPerCPU=0
FastSchedule=1
#MaxMemPerCPU=0
#SchedulerRootFilter=1
SchedulerTimeSlice=30
PreemptMode=cancel
PreemptType=preempt/partition_prio
#PreemptType=preempt/qos
SchedulerType=sched/backfill
SchedulerPort=7321
#SelectType=select/linear
SelectType=select/cons_res
SelectTypeParameters=CR_Core_Memory
#PreemptMode=GANG
#
#
# JOB PRIORITY
PriorityType=priority/multifactor
#PriorityDecayHalfLife=PriorityMaxAge=10
#PriorityUsageResetPeriod=
PriorityWeightAge=100000
#PriorityWeightFairshare=1000
PriorityWeightJobSize=1000
PriorityWeightPartition=1000
#

--

Regards,

Yogendra
#PriorityCalcPeriod=
PriorityFavorSmall=Yes

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.

www.wipro.com<http://www.wipro.com>
Error! Filename not specified.



--
--
Carles Fenoy


Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.

www.wipro.com

<<inline: image001.jpg>>

Reply via email to