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

Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/08/29 18:12:00 UTC

[jira] [Updated] (YUNIKORN-2452) Use RLock() for node.GetAvailableResource()

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

Craig Condit updated YUNIKORN-2452:
-----------------------------------
    Summary: Use RLock() for node.GetAvailableResource()   (was: node.go#GetAvailableResource ought to use read-lock instead of readwrite-lock )

> Use RLock() for node.GetAvailableResource() 
> --------------------------------------------
>
>                 Key: YUNIKORN-2452
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2452
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>            Reporter: Chia-Ping Tsai
>            Assignee: Yun Sun
>            Priority: Minor
>              Labels: newbie, pull-request-available
>
> see [https://github.com/apache/yunikorn-core/blob/master/pkg/scheduler/objects/node.go#L264]
> The other similar methods (`GetAllocatedResource`, `GetOccupiedResource`, and `GetCapacity`) are using read-lock, so `GetAvailableResource` ought to apply read-lock too.



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