Ticket 8763 - threadsafety of jobacct_gather/cgroup
Summary: threadsafety of jobacct_gather/cgroup
Status: RESOLVED DUPLICATE of ticket 8656
Alias: None
Product: Slurm
Classification: Unclassified
Component: slurmd (show other tickets)
Version: 20.11.x
Hardware: Linux Linux
: --- 5 - Enhancement
Assignee: Unassigned Developer
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2020-03-31 12:24 MDT by Nate Rini
Modified: 2020-08-18 14:53 MDT (History)
2 users (show)

See Also:
Site: SchedMD
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: ---


Attachments

Note You need to log in before you can comment on or make changes to this ticket.
Description Nate Rini 2020-03-31 12:24:01 MDT

    
Comment 1 Nate Rini 2020-03-31 12:25:16 MDT
Multiple race conditions have been found (bug #8656 and bug #7617) suggesting the whole jobacct_gather/cgroup plugin needs to be verified for thread safety.
Comment 2 Felip Moll 2020-04-01 04:05:05 MDT
The cgroup plugins have races between them on the management of cgroups.

https://bugs.schedmd.com/show_bug.cgi?id=7536
Comment 3 Tim Wickberg 2020-08-06 19:15:14 MDT
Is this bug meant to capture anything that's not already on bug 8656, or one of the other cgroup cleanup tickets? (I'll note Danny has already done a large amount of cleanup on master in July, and this may or may not still be a concern after that refactoring went through.)

If not, please close as a duplicate.
Comment 4 Nate Rini 2020-08-18 14:53:19 MDT
(In reply to Tim Wickberg from comment #3)
> Is this bug meant to capture anything that's not already on bug 8656, or one
> of the other cgroup cleanup tickets? (I'll note Danny has already done a
> large amount of cleanup on master in July, and this may or may not still be
> a concern after that refactoring went through.)
> 
> If not, please close as a duplicate.

done

*** This ticket has been marked as a duplicate of ticket 8656 ***