The intent behind the partition priority being used but given a weight of 0 is that the priorities we use for partitions are for preemption logic only. So far I've only been able to reproduce this problem on my account, so waiting to see if users will have same issue now that we're production with SLURM.
Thanks, - Trey ============================= Trey Dockendorf Systems Analyst I Texas A&M University Academy for Advanced Telecommunications and Learning Technologies Phone: (979)458-2396 Email: [email protected] Jabber: [email protected] On Wed, Oct 29, 2014 at 5:00 AM, Yann Sagon <[email protected]> wrote: > > > 2014-10-24 18:49 GMT+02:00 Trey Dockendorf <[email protected]>: > >> >> PriorityWeightPartition=0 # 0% >> >> Example of a stakeholder partition and background: >> >> PartitionName=hepx Nodes=c0[101-116,120-132,227,416,530-532,933-936] >> Priority=100 AllowQOS=hepx MaxNodes=1 MaxTime=120:00:00 State=UP >> PartitionName=background Priority=10 AllowQOS=background MaxNodes=1 >> MaxTime=96:00:00 State=UP >> >> >> Hello, It seems wrong to me to define a PriorityWeightPartition=0 and to > define a priority in your partitions. Not sure that this will change > something to your problem anyway. >
