You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2024/04/07 13:57:00 UTC

[jira] [Resolved] (YUNIKORN-2546) Eliminate read lock call from Queue.addChildQueue()

     [ https://issues.apache.org/jira/browse/YUNIKORN-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Bacsko resolved YUNIKORN-2546.
------------------------------------
    Resolution: Duplicate

Closing as duplicate. No need for two JIRAs.

> Eliminate read lock call from Queue.addChildQueue()
> ---------------------------------------------------
>
>                 Key: YUNIKORN-2546
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2546
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: core - scheduler
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>
> Do not acquire a read lock on the Queue while running {{Queue.addChildQueue()}} due to its unsafe nature. That is, do not call {{Queue.GetCurrentPriority()}}, replace it with a lockless variant.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org