Raw usage is captured and saved locally to the cluster in the assoc_usage file in your configured StateSaveLocation. The values saved there are subject to half life decay based on your PriorityDecayHalfLife setting. These values can be forcibly reset to zero by running “sacctmgr modify account <xxx> set RawUsage=0”.
Usage values saved to the SLURM db do not decay. sreport retrieves these values from the db to generate its reports. I’m not sure what's going on with sprio. Don > -----Original Message----- > From: [email protected] [mailto:owner-slurm- > [email protected]] On Behalf Of Loris Bennett > Sent: Friday, February 10, 2012 6:30 AM > To: [email protected] > Subject: [slurm-dev] Problem with setting up fairshare > > Hi, > > I am trying to set up fairshare scheduling and can send details of the > configuration, but I wondered whether there was a simple explanation of > the following: > > sshare shows "Raw Usage" of zero for all accounts, whereas sreport > shows > non-zero CPU usage. Also sprio on its own returns nothing and the > following if given an existing job ID: > > # sprio -j 12345 > Unable to find jobs matching user/id(s) specified > > Any ideas? > > Cheers > > Loris > -- > Dr. Loris Bennett (Mr.) > ZEDAT, Freie Universität Berlin Email loris.bennett@fu- > berlin.de >
