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

Posted to issues@yunikorn.apache.org by "Manikandan R (Jira)" <ji...@apache.org> on 2022/07/25 16:00:01 UTC

[jira] [Commented] (YUNIKORN-1264) Refactor asks and allocations to use consistent locking

    [ https://issues.apache.org/jira/browse/YUNIKORN-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570973#comment-17570973 ] 

Manikandan R commented on YUNIKORN-1264:
----------------------------------------

Is there any plan for us to follow locks refactoring even for other objects? If so, we can bring them all in single umbrella jira for tracking.

> Refactor asks and allocations to use consistent locking
> -------------------------------------------------------
>
>                 Key: YUNIKORN-1264
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1264
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - scheduler
>            Reporter: Craig Condit
>            Assignee: Craig Condit
>            Priority: Major
>              Labels: pull-request-available
>
> In the core scheduler, the ask and allocation objects use inconsistent locking / access patterns. These should be refactored to use strong encapsulation (getters for read/only, getters/setters for mutable values using locks).



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