Hi Nagraj,
You can for example limit a number of running jobs in the cms queue:
qmgr -c "set queue cms max_running=199"
But this is impractical, since other VOs can flood their queues as well.
If you are using maui, you can also make a one-cpu reservation for ops
class:
cat >> /var/spool/maui/maui.cfg <<EOF
SRCFG[forops] PERIOD=INFINITY
SRCFG[forops] RESOURCES=PROCS:1
SRCFG[forops] CLASSLIST=ops
EOF
service maui restart
You can find a more detailed information on reservations here:
http://www.clusterresources.com/products/maui/docs/7.1.5managingreservations.shtml
As for the DN of the submitting users, simply read qstat -a, find local
username associated with the job and then you can find DN of that user
via a hard link referring to that username in /etc/grid-security/gridmapdir
For example, if you want to find DN of user dteam003 you do:
ls -li |grep `ls -li dteam003 |cut -f 1 --delim=' '`
As for the edg-job ID I don't think you can find this information on
local CE without having access to WMS logs.
Best regards,
Adam
Nagaraj Panyam wrote:
> Hi,
>
> I have some novice questions.
>
> At our site, we see a long queue of 200 jobs by user cms jobs, and
> SAM jobs are kept waiting. How do I manage the situation? How do I
> make sure that dteam and ops jobs get to run without waiting long?
>
> How do I know what is the id of the edg-job that is running , who
> submitted etc?
>
> Thanks
> Nagaraj
> +----------------------------------+--------------------------------------+
>
> Nagaraj Panyam | Office tel: +91-22-22782610
> Dept of High Energy Physics | Office fax: +91-22-22804610
> Tata Instt. of Fundamental Research| Home tel : +91-22-22804936
> Mumbai - 400 005, INDIA | **Email** : [log in to unmask]
> +----------------------------------+--------------------------------------+
>
|