Ticket 4798

Summary:	MariaDB lock problems for sacctmgr delete query
Product:	Slurm	Reporter:	Ole.H.Nielsen <Ole.H.Nielsen>
Component:	Database	Assignee:	Tim Wickberg <tim>
Status:	RESOLVED INFOGIVEN	QA Contact:
Severity:	4 - Minor Issue
Priority:	---
Version:	17.11.3
Hardware:	Linux
OS:	Linux
Site:	DTU Physics	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 Ole.H.Nielsen@fysik.dtu.dk 2018-02-16 05:51:52 MST

This is just a question related to our plans to upgrade from 17.02 to 17.11:

I'd like to ensure a smooth upgrading experience, so I'm worried about the issue "MariaDB lock problems for sacctmgr delete query" reported to the slurm-users list on Feb. 13.  Apparently SchedMD has a bug fix in Bug 4785, but we're not allowed to see it.

Questions:

1. Will Bug 4785 be resolved in 17.11.4?

2. Is it likely that an upgrade from 17.02 to 17.11 will encounter this issue?

FYI:
I've already made a dry run test upgrade of our 17.02.9 database to 17.11.3 without encountering any problems.  I reported this to the slurm-users list on Feb. 16.  My dry run upgrade procedure is documented in
https://wiki.fysik.dtu.dk/niflheim/Slurm_installation#make-a-dry-run-database-upgrade

Thanks,
Ole

Comment 1 Tim Wickberg 2018-02-16 08:23:15 MST

(In reply to Ole.H.Nielsen@fysik.dtu.dk from comment #0)
> This is just a question related to our plans to upgrade from 17.02 to 17.11:
> 
> I'd like to ensure a smooth upgrading experience, so I'm worried about the
> issue "MariaDB lock problems for sacctmgr delete query" reported to the
> slurm-users list on Feb. 13.  Apparently SchedMD has a bug fix in Bug 4785,
> but we're not allowed to see it.
> 
> Questions:
> 
> 1. Will Bug 4785 be resolved in 17.11.4?

No.

The entirety of the bug was some internal discussion leading to this commit on the master branch, which will be 18.08.0-pre2 and up:

https://github.com/SchedMD/slurm/commit/4a16541bf0e00

It leads to a small change in behavior (association ids are no longer densely packed), and thus was not considered appropriate for a maintenance release.

> 2. Is it likely that an upgrade from 17.02 to 17.11 will encounter this
> issue?

No. If you're not seeing issues now, you likely won't in 17.11.

You'll note Jessica's email mentions a switch in their database at the same time - I'm guessing there is some other relevant changes that exposed this as an issue.

The AUTO_INCREMENT behavior itself has remained unchanged for quite a while - it's much older than 17.02.

Preemptively tagging this as resolved/infogiven; please reopen if you have any further questions.

- Tim

Comment 2 Ole.H.Nielsen@fysik.dtu.dk 2018-02-16 08:26:30 MST

(In reply to Tim Wickberg from comment #1)
Thanks Tim!  This sounds good to me.
/Ole