DOKK / manpages / debian 12 / slurm-client / sshare.1.en
sshare(1) Slurm Commands sshare(1)

sshare - Tool for listing the shares of associations to a cluster.

sshare [OPTIONS...]

sshare is used to view Slurm share information. This command is only viable when running with the priority/multifactor plugin. The sshare information is derived from a database with the interface being provided by slurmdbd (Slurm Database daemon) which is read in from the slurmctld and used to process the shares available to a given association. sshare provides Slurm share information of Account, User, Raw Shares, Normalized Shares, Raw Usage, Normalized Usage, Effective Usage, the Fair-share factor, the GrpTRESMins limit, Partitions and accumulated currently running TRES-minutes for each association.

Display information for specific accounts (comma separated list).

Display information for all users.

Clusters to issue commands to. Note that the SlurmDBD must be up for this option to work properly.

Comma separated list of fields (use "--helpformat" for a list of available fields).

Display a description of sshare options and commands.

Long listing - includes the normalized usage information.

No header will be added to the beginning of the output.

Output will be '|' delimited with a '|' at the end.

Output will be '|' delimited without a '|' at the end.

If there are association based partitions in the system print their names.

Display a description of sshare options and commands.

Display information for specific users (comma separated list).

If specified only the users information are printed, the parent and ancestors are not displayed.

Display more information about the specified options.

Display the version number of sshare.

The Account.

The User.

The raw shares assigned to the user or account.

The shares assigned to the user or account normalized to the total number of assigned shares.

The number of tres-seconds (cpu-seconds if TRESBillingWeights is not defined) of all the jobs charged to the account or user. This number will decay over time when PriorityDecayHalfLife is defined.

The Raw Usage normalized to the total number of tres-seconds of all jobs run on the cluster, subject to the PriorityDecayHalfLife decay when defined.

The Effective Usage augments the normalized usage to account for usage from sibling accounts.

The Fair-Share factor, based on a user or account's assigned shares and the effective usage charged to them or their accounts.

The TRES-minutes limit set on the account. The total number of cpu minutes that can possibly be used by past, present and future jobs running from this account and its children.

The raw TRES usage that has been used by jobs running from this account and its children.

The number of TRES-minutes allocated by jobs currently running against the account. Used to limit the combined total number of TRES minutes used by all jobs running with this account and its children. This takes into consideration time limit of running jobs and consumes it, if the limit is reached no new jobs are started until other jobs finish to allow time to free up.

When PriorityFlags=FAIR_TREE is set (the default, unless NO_FAIR_TREE is set), calculations are done differently. As a result, the following fields are added or modified:

The shares assigned to the user or account normalized to the total number of assigned shares within the level.

Effectv Usage is the association's usage normalized with its parent.

This is the association's fairshare value compared to its siblings, calculated as Norm Shares / Effectv Usage. If an association is over-served, the value is between 0 and 1. If an association is under-served, the value is greater than 1. Associations with no usage receive the highest possible value, infinity.

More information about Fair Tree can be found in doc/html/fair_tree.html or at https://slurm.schedmd.com/fair_tree.html

Executing sshare sends a remote procedure call to slurmctld. If enough calls from sshare or other Slurm client commands that send remote procedure calls to the slurmctld daemon come in at once, it can result in a degradation of performance of the slurmctld daemon, possibly resulting in a denial of service.

Do not run sshare or other Slurm client commands that send remote procedure calls to slurmctld from loops in shell scripts or other programs. Ensure that programs limit calls to sshare to the minimum necessary for the information you are trying to gather.

Some sshare options may be set via environment variables. These environment variables, along with their corresponding options, are listed below. (Note: Command line options will always override these settings.)

The location of the Slurm configuration file.

Specify debug flags for sshare to use. See DebugFlags in the slurm.conf(5) man page for a full list of flags. The environment variable takes precedence over the setting in the slurm.conf.

$ sshare -A <Account>

$ sshare --parsable --users=<User>

Copyright (C) 2008 Lawrence Livermore National Security. Produced at Lawrence Livermore National Laboratory (cf, DISCLAIMER).
Copyright (C) 2010-2022 SchedMD LLC.

This file is part of Slurm, a resource management program. For details, see <https://slurm.schedmd.com/>.

Slurm is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

Slurm is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

slurm.conf(5), slurmdbd(8)

Slurm Commands August 2022