[Mauiusers] Problem with Account Management and Maui 3.3.1

Brian Mendenhall brianm at usc.edu
Wed Sep 21 11:17:40 MDT 2011


I apologize as I don't think I made my goal clear;

> So now my question is: is it really just that you either have an
> Allocation Manager and everyone gets charged, or is there a
> different way to accomplish the same goal?

my goal is to allow a class of node or a group (unix account GID) to *not* be charged for running jobs on that queue/node type.

-----
Brian Mendenhall
Linux/HPCC Administrator
University of Southern California

----- Original Message -----
From: Brian Mendenhall <brianm at usc.edu>
Date: Wednesday, September 21, 2011 10:05 am
Subject: Re: [Mauiusers] Problem with Account Management and Maui 3.3.1
To: mauiusers at supercluster.org

> Thank you for your reply Roy.
> 
> I installed and tested Gold, but did not feel like it brought 
> anything sufficient enough to justify losing all of our historical 
> qbank data (the databases are not compatible, no real migration 
> utilities exist, and I don't have the time to create them), but I 
> guess I did miss this 'nocharge' issue as I was under the 
> impression it was part of maui.
> 
> I did, however, find an old patch for maui 3.2.6.p20 that 
> implemented the 'NOAM' CLASSCFG feature, so this explains how it 
> used to work.
> 
> So now my question is: is it really just that you either have an 
> Allocation Manager and everyone gets charged, or is there a 
> different way to accomplish the same goal?
> 
> I do see that NODECFG has a feature of 'CHARGERATE', but it would 
> not be feasible for me to have 2700+ entries in my maui.cfg, unless 
> I can use something like 'NODECFG[cmb] CHARGERATE=0.0' which would 
> be applied to the nodeset feature 'cmb'.
> 
> Going to try to test it without causing problems ...
> 
> -----
> Brian Mendenhall
> Linux/HPCC Administrator
> University of Southern California
> 
> ----- Original Message -----
> From: Roy Dragseth <roy.dragseth at cc.uit.no>
> Date: Wednesday, September 21, 2011 12:46 am
> Subject: Re: [Mauiusers] Problem with Account Management and Maui 
> 3.3.1To: mauiusers at supercluster.org
> 
> > We switched from qbank to gold a long time ago so I'm not sure if 
> > this applies 
> > to qbank.  In gold you can set the chargerate to 0 for a specific 
> > QoS, maybe 
> > something similar is possible in qbank.
> > 
> > r.
> > 
> > 
> > On Wednesday, September 21, 2011 07:03:34 Brian Mendenhall wrote:
> > > I have recently upgraded torque and maui on my cluster and have 
> > run into a
> > > weird issue that I am having a hard time understanding why I 
> > can't find
> > > any documentation on the subject.
> > > 
> > > Maui: 3.3.1 (upgraded from 3.2.6)
> > > RM: Torque 2.4.16 (upgraded from 2.1.12)
> > > AM: Qbank: 2.11 (not upgraded)
> > > 
> > > Previously, I had torque queues for users that are not charged 
> > time for
> > > running their jobs, as an example, lets say people that belong 
> to 
> > the unix
> > > group 'lc_cmb' submit jobs to the 'cmb' queue using 'qsub -q cmb
> > > script.pbs'. The maui.cfg entry for cmb was:
> > > 
> > > CLASSCFG[cmb]           NOAM=TRUE JOBFLAGS=SHAREDIFSINGLENODE
> > > MAXJOB[USER]=300,420
> > > 
> > > and that basically turned off any charges for the cmb group.
> > > 
> > > I know that qbank is working fine, and maui <-> interaction is 
> > fine because
> > > regular users that do get charged time work fine.
> > > 
> > > Is there a different way of turning off account management 
> > charges for
> > > queues in maui/torque/qbank?
> > > 
> > > The error in the maui.log file is pretty simple:
> > > 09/20 21:49:48 INFO:     transaction sent to AM
> > > 09/20 21:49:48 ALERT:    cannot create AM reservation for job 
> '1324'> > (request refused) 09/20 21:49:48 ERROR:    cannot start 
> job 
> > '1324' in
> > > partition DEFAULT
> > > 
> > > Awaiting 00000237 bytes -- Tue Sep 20 21:28:22 PDT 2011
> > > REQUEST=COMMAND=make_reservation AUTH=maui MACHINE=hpc 
> > ACCOUNT=lc_cmb> USER=sungjech WCLIMIT=86400 PROCCOUNT=16 
> > QOS=DEFAULT CLASS=cmb_exe
> > > NODETYPE=DEFAULT TYPE=maui JOBID=1324 JOBTYPE=job NODES=1 
> > REPLY=00000072> STATUSCODE=0 RESULT=sungjech does not have 
> > sufficient funds for job 1324
> > > 
> > > I find this weird:
> > > [root at hpc-pbs maui]$ showconfig | grep '\[cmb\]'
> > > CLASSCFG[cmb]  DEFAULT.FEATURES=[cmb]
> > > 
> > > [root at hpc-pbs maui]$ diagnose -v -c cmb
> > > Class/Queue Status
> > > 
> > > Name           Priority Flags        QDef              QOSList*
> > > PartitionList        Target Limits
> > > 
> > > cmb                   0 [NONE]       [NONE]             [NONE]  
> > [NONE]     
> > >           0.00  [NONE] DEFAULT.FEATURES=[cmb]  
> MAXJOBPERUSER=420,300> > 
> > > So, the maxjob configuration is there, but no JOBFLAGS or NOAM
> > > configurations shown.
> > > 
> > > -----
> > > Brian Mendenhall
> > > Linux/HPCC Administrator
> > > University of Southern California
> > > _______________________________________________
> > > mauiusers mailing list
> > > mauiusers at supercluster.org
> > > http://www.supercluster.org/mailman/listinfo/mauiusers
> > _______________________________________________
> > mauiusers mailing list
> > mauiusers at supercluster.org
> > http://www.supercluster.org/mailman/listinfo/mauiusers
> > 
> _______________________________________________
> mauiusers mailing list
> mauiusers at supercluster.org
> http://www.supercluster.org/mailman/listinfo/mauiusers
> 


More information about the mauiusers mailing list