Ticket 17034

Summary:	Enhancement request to support higher MaxJobId
Product:	Slurm	Reporter:	azoshima
Component:	Configuration	Assignee:	Jason Booth <jbooth>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	4 - Minor Issue
Priority:	---	CC:	gphipps, ihmesa
Version:	22.05.8
Hardware:	Linux
OS:	Linux
Site:	U WA Health Metrics	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 azoshima 2023-06-22 15:01:48 MDT

Hello support team,

Do you have any plan to support higher MaxJobId more than 67,108,863? 

It would be very helpful to keep track old jobs if the job_id is unique. With large workflow or array jobs, they will consume jobid quickly and will end up restarting job_id from 1.

Thank you,

Comment 2 Jason Booth 2023-06-22 15:57:37 MDT

> Do you have any plan to support higher MaxJobId more than 67,108,863? 

Unfortunately, we don't have plans to change JobId in the near future. There are 
some technical roadblocks with expanding this that make this undesirable. We could 
consider the possibility of introducing unique identifiers for each job, different 
from JobID, that would never repeat similar to say UUIDs, however this would be 
something that a site would need to sponsor the development for. Would your site 
be interested in sponsoring such a feature?

Comment 3 Jason Booth 2023-07-11 09:42:20 MDT

Since I have not heard back from you I will move to resolve this issue out. Should
your site be interested in discussing sponsorship of this feature then please feel
free to re-open this issue.