Unfortunately I had to clear them out to fit some jobs in.. but I have a
similar comparison:
]# diagnose -p | more
diagnosing job priority information (partition: ALL)
Job PRIORITY* Cred( QOS:Class) Serv(QTime)
Weights -------- 1( 1: 1) 1( 1)
258693 10076 1.0( 0.0:100.0) 99.0(9975.)
258704 10076 1.0( 0.0:100.0) 99.0(9975.)
258705 10076 1.0( 0.0:100.0) 99.0(9975.)
258708 10076 1.0( 0.0:100.0) 99.0(9975.)
258714 10076 1.0( 0.0:100.0) 99.0(9975.)
258474 9949 1.0( 0.0:100.0) 99.0(9849.)
258463 9810 1.0( 0.0:100.0) 99.0(9709.)
These top jobs with 10,000+ are preempted, originally had 100 priority.
Currently they are suspended.
-----Original Message-----
From: Troy Baer [mailto:[email protected]]
Sent: Wednesday, December 14, 2011 4:12 PM
To: Edsall, William (WJ)
Cc: [email protected]
Subject: Re: [Mauiusers] queue priority including wait time?
On Wed, 2011-12-14 at 15:57 -0500, Edsall, William (WJ) wrote:
> We have been using a Preemptee queue called overflow. The queue has a
> priority of 100 while the other queues default to 10000 priority.
>
> A user had queued up extra jobs in overflow, and it these queued jobs
> seemed to block any new priority queue jobs. Could it have been
> because they were in the queue so long, their priority went up? How
> can we disable this for a specific queue? If this is a fairshare
> setting we are using fairshare defaults.
What does "diagnose -p" say?
--Troy
--
Troy Baer, HPC System Administrator
National Institute for Computational Sciences, University of Tennessee
http://www.nics.tennessee.edu/
Phone: 865-241-4233
_______________________________________________
mauiusers mailing list
[email protected]
http://www.supercluster.org/mailman/listinfo/mauiusers
