Ticket 9339

Summary:	Utilization "Reported"
Product:	Slurm	Reporter:	Amit Kumar <ahkumar>
Component:	Configuration	Assignee:	Gavin D. Howard <gavin>
Status:	RESOLVED TIMEDOUT	QA Contact:
Severity:	4 - Minor Issue
Priority:	---
Version:	19.05.2
Hardware:	Linux
OS:	Linux
Site:	SMU	Alineos Sites:	---
Atos/Eviden Sites:	---	Confidential Site:	---
Coreweave sites:	---	Cray Sites:	---
DS9 clusters:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Linux Distro:	---
Machine Name:		CLE Version:
Version Fixed:		Target Release:	---
DevPrio:	---	Emory-Cloud Sites:	---

Description Amit Kumar 2020-07-06 12:45:27 MDT

Dear SchedMD, 

I thought I understood what cluster utilization output term "Reported" meant at one point, but can't seem to make sense out of it at the moment. Can you please help me understand this??

Also Can you please explain why would sreport report reported time below 100%?
#sreport -P  -t per  clust util start=x/y/z end=a/b/c  
Cluster|Allocated|Down|PLND Down|Idle|Reserved|Reported
slurm_cluster|57.48%|4.73%|0.01%|29.61%|8.18%|99.80% 

Thank you,
Amit

Comment 1 Gavin D. Howard 2020-07-06 14:16:29 MDT

Thank you for the question. I will get back to you as soon as I can.

Comment 2 Gavin D. Howard 2020-07-14 12:45:58 MDT

In order to answer your questions better, I would like to have your slurm.conf.

My first thought about the 99.80% reported time is that it is actually the result of inexact floating point arithmetic, but it also depends on your partitions.

Comment 3 Gavin D. Howard 2020-07-27 11:04:22 MDT

This is a reminder to give me your slurm.conf.

Comment 4 Gavin D. Howard 2020-08-10 14:21:51 MDT

Because I have not heard back in a while, I am closing this bug.