[GE users] How to check reservations?

gutnik gutnik at gmail.com
Mon Aug 30 21:29:52 BST 2010


    [ The following text is in the "utf-8" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some characters may be displayed incorrectly. ]

On Mon, Aug 30, 2010 at 12:31 PM, reuti <reuti at staff.uni-marburg.de> wrote:
> Am 30.08.2010 um 19:47 schrieb gutnik:
>
>> I'm having trouble running a big job that takes multiple CPUs while
>> there is a steady stream of smaller jobs.
>>
>> As I understand
>> http://wikis.sun.com/display/GridEngine/Managing+the+Scheduler, the
>> way to ensure the bigger
>> job gets run is to submit it with the -R y flag, so that once it
>> becomes the top priority job it will start to reserve
>> resources (in this case, CPU slots), until it runs. Is that right?
>>
>> (In this case, the job is being submitted with a pe environment that
>> requires 12 slots on one machine.)
>>
>> So, just now, I increased the priority of the job and it is now at the
>> top of the queue, as reported by qstat. Is there some way
>> to see that a)  the reservation is in place and b) that resources are
>> being held for this job?
>
> You can set "MONITOR=1" in the scheduler "params" and check the output of the "schedule" file (`man sched_conf`).

I set MONITOR=1. Now "schedule" file has a bunch of information, but
the job I care about doesn't show up at all. Should it?

> Do you specify a runtime ("h_rt") for the jobs? Otherwise the default_duration "unlimited" from the scheduler is taken, which judges "unlimited" as being smaller than "unlimited" (of the already running jobs w/o a runtime limit) and following jobs without a given runtime might slip in all the time. Setting the default_duration to 9999:99:99 might help if this is the case.

h_rt is set.

   Vadim

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=278307

To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list