Ticket 903

Summary:	/var/spool/slurmd as a memory resident file system
Product:	Slurm	Reporter:	Stuart Midgley <stuartm>
Component:	slurmd	Assignee:	David Bigagli <david>
Status:	RESOLVED INFOGIVEN	QA Contact:
Severity:	4 - Minor Issue
Priority:	---	CC:	da
Version:	14.03.4
Hardware:	Linux
OS:	Linux
Site:	DownUnder GeoSolutions	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:	---

Description Stuart Midgley 2014-06-22 19:26:21 MDT

Afternoon

Is their any reason not to run /var/spool/slurmd as a memory resident file system?  ie. its contents won't survive a reboot?

Comment 1 Moe Jette 2014-06-23 02:35:58 MDT

That directory is used by the slurmd daemon to store job state information that it can recover when the daemon restarts. It can be purged on a reboot since the running jobs will not survive so their state information is not useful.