You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2024/02/22 05:59:00 UTC

[jira] [Created] (YUNIKORN-2445) Add comments around locking setup in tracker code

Wilfred Spiegelenburg created YUNIKORN-2445:
-----------------------------------------------

             Summary: 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


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: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org