(r2) SunGridEngineAdmin < BETA

Tags: view all tags
---+ Sun Grid Engine Administration

%TOC%

For general information about _using_ Sun Grid Engine, see SunGridEngine.

---++ Checking the queque
qstat gives basic information about the jobs in the queque<br>
qstat -ext gives a bit of extra information, such as a job's project <br>
qstat -j &lt;jobnumber&gt; gives you very detailed information about that job

Is there a way to change the project of a running job?  That could be useful someday...

---++ Override Policy

This is the primary mechanism that is used to determine which jobs are dispatched.  Go to Policy Configuration and then Override Policy.  Choose "project" from the dropdown, and you'll see all the SGE project names with the number of override tickets they get.  They should always be multiples of 10,000: this ensures that override tickets trump share tree tickets (of which there are 9,000, as set on the main policy configuration page). Higher priority projects preempt lower priority ones--as long as their tickets are multiples of 10,000, no jobs will be run from a lower-priority project while pending jobs from a higher-priority project exist.  You can modify the number of tickets a project is given here, but you can't create a new one.  To do that, go to "Project Configuration" from the main qmon dialog.

---++ Share Tree Policy

This is the policy that is used to determine how competing jobs are scheduled when they fall within the same project.
To change the share tree policy, go to Policy Configuration and click on Share Tree Policy. Right now, for each project (eh, ea, Urgent, etc), there is a node in the graph with a leaf called default. (If you don't see the leaf, double-click on the node to open it up.) Under this default leaf, SGE automatically adds all users in that project--they're listed inside. What this does is to ensure that all users in the project get the same priority, so that SGE will ensure that each user gets the same amount of CPU time (not the same number of jobs) within the same time window. Of course, the share tree policy doesn't have to share resources evenly. You can add another leaf named after a specific user to give them extra shares (they're proportional to the entry for Shares).

---++ Adding a new user:

Go to User Configuration, click on Userset, select the appropriate Userset, click on modify and enter the username. The following usersets are mutually exclusive (a user only needs to be added to one, and should be added to the one which is highest on the list to which he belongs):
   * EH-Models
   * !EmpiricalAlgorithmics
   * KLB
   * General
The other usersets are different: a user who belongs to one of the above sets can also belong to them.  It is *important* to add every user to the userset called arrow--if you do not, the user will be able to submit jobs but they may not ever run.  Users need to belong to urgentusers to submit urgent jobs.


-- Main.FrankHutter - 11 Oct 2006
Topic revision: r2 - 2006-10-12 - KevinLeytonBrown