Ticket 1434

Summary:	Constraints not visible in sacct
Product:	Slurm	Reporter:	Marco Passerini <marco.passerini>
Component:	Accounting	Assignee:	Unassigned Developer <dev-unassigned>
Status:	CONFIRMED ---	QA Contact:
Severity:	5 - Enhancement
Priority:	---
Version:	14.11.3
Hardware:	Linux
OS:	Linux
Site:	CSC - IT Center for Science	Alineos Sites:	---
Atos/Eviden Sites:	---	Confidential Site:	---
Coreweave sites:	---	Cray Sites:	---
DS9 clusters:	---	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:	---

Description Marco Passerini 2015-02-05 01:38:20 MST

Our users are using constraint options to pick processor types, like:
srun -n 1 --constraint=haswell hostname

Is there a way to visualize whether a job has been using a given constraint in sacct and squeue? I didn't manage to do it.

If it's not available, that would be a nice feature to have.

Comment 1 Moe Jette 2015-02-25 04:48:20 MST

The information is available using the "scontrol show job #" command or the squeue command with a user-specified output format. That would be something of this sort

squeue -O jobid,features

Note that user's can specify their default format using the "SQUEUE_FORMAT2" environment variable (e.g. "export SQUEUE_FORMAT2=jobid,feature").

The information is current not recorded in the accounting database, so it is not visible using the sacct command.

Comment 2 Marco Passerini 2015-02-26 00:46:48 MST

Thanks, for pointing these features out, it's very useful information!
I'll follow the Slurm releases to see if it gets added to sacct. It would be useful.