Ticket 10382 - sreport man page
Summary: sreport man page
Status: RESOLVED INVALID
Alias: None
Product: Slurm
Classification: Unclassified
Component: Documentation (show other tickets)
Version: 19.05.7
Hardware: Linux Linux
: 6 - No support contract
Assignee: Jacob Jenson
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2020-12-07 10:01 MST by DS
Modified: 2020-12-07 13:16 MST (History)
0 users

See Also:
Site: -Other-
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description DS 2020-12-07 10:01:58 MST 
Please can the exact nature of the sreport cluster Utilization Down figure be explained. The man page reads:

 Down         Time that nodes were marked as Down or time that slurmctld was not responding (assuming TrackSlurmctldDown is set in slurmdbd.conf).


Does these mean all nodes are treated equally or are cores on nodes taken into account?

thanks