[Mauiusers] MAXNODES broken?
hyrum at supercluster.org
Fri Oct 29 15:31:27 MDT 2004
Maui only enforces node usage limits if the nodecount is explicitly
specified by the job. In many cases, only a task or processor count is
specified with the job and the node usage limit is ineffective. Maui
filters jobs based on policies, then determines which nodes are
available to jobs, then maps processors requested to available nodes.
Because of this, if no node count is explicitly specified, maui does not
know node mappings until after the job has been selected. Processor
based usage limits may work better in your environment.
Moab 4.2 and higher uses a more advanced job selection algorithm and
is able to determine node usage early and enforce MAXNODE limits even
when node usage is not explicitly specified.
Please let us know if we can assist you further.
On Thu, 2004-10-28 at 10:32, Michael Shuey wrote:
> Does the MAXNODES limit actually work in recent versions of Maui? I've
> tried 3.2.6p9, p10, and p11-snap.1090086588, but none behave as
> expected. I've added this to my maui.cfg:
> CLASSCFG[testq] MAXNODE=2 MAXJOB=100 MAXPROC=10
> When I run diagnose -c testq (after submitting a single job), I see:
> Class/Queue Status
> Name Priority Flags QDef QOSList*
> PartitionList Target Limits
> testq 0 [NONE] [NONE] [NONE]
> [NONE] 0.00 MAXJOB=1:100 MAXNODE=0:2 MAXPROC=1:10
> So, it looks like maui notices that a job is running, and it realizes
> that it's a single-proc job, but it doesn't increment the number of
> nodes in use. Further poking proves I can submit, and maui will
> schedule, jobs that use more than 2 nodes (as long as they don't exceed
> the 10-processor limit).
> Is this a bug, or am I missing something?
More information about the mauiusers