[ https://issues.apache.org/jira/browse/YUNIKORN-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai resolved YUNIKORN-2445. -------------------------------------- Fix Version/s: 1.5.0 Resolution: Fixed > Add comments around locking setup in tracker code > ------------------------------------------------- > > Key: YUNIKORN-2445 > URL: https://issues.apache.org/jira/browse/YUNIKORN-2445 > Project: Apache YuniKorn > Issue Type: Task > Components: core - scheduler > Reporter: Wilfred Spiegelenburg > Assignee: Yu-Lin Chen > Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > > The QueueTracker code is lock free and should stay lock free. Each queue > tracker object is always only linked to one UserTracker or GroupTracker. > Locking is thus handled from those objects. > This does mean that calls to the user or group trackers that can modify the > underlying queue tracker structure must take a write lock. > This specifically impacts the {{canRunApp()}} and {{headroom()}} calls as > they add new entries in the queue hierarchy. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org