[gridengine users] Long delay starting jobs, even when compute nodes are empty
dowobeha at gmail.com
Fri Mar 11 14:07:49 UTC 2011
On Fri, Mar 11, 2011 at 8:58 AM, Reuti <reuti at staff.uni-marburg.de> wrote:
> Am 11.03.2011 um 14:49 schrieb Lane Schwartz:
> > Rayson,
> > Thanks for the pointer. In the qmon scheduler configuration, I have
> > "Job Scheduling Information" set to true. I assume that's the same
> > setting you're refering to?
> > With this setting enabled, I still don't get very much info. When I
> > run qstat -j on my jobs, the only thing it tells me is that a queue
> > instance for a particular node is dropped because that node is
> > disabled.
> Because "disabled"? Did someone use `qmon` to disable the node or set up
> any calendar?
I believe our sysadmin intentionally disabled that particular node. The
queue instance all.q at quad2 dropped because it is disabled
I do know that more scheduling info can be printed out. There's currently a
job waiting in the queue that asked for mem_free=40960M, and when I run
qstat -j on that job, I get a bunch of output saying that the job can't be
run on various hosts because they don't offer enough mem_free.
But, for most of my queued jobs, scheduling info only prints out the message
about the disabled node.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users