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

Posted to dev@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/01/19 18:54:00 UTC

[jira] [Resolved] (YUNIKORN-2329) Ensure RMProxy events are processed in-order

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

Craig Condit resolved YUNIKORN-2329.
------------------------------------
     Fix Version/s: 1.5.0
    Target Version: 1.5.0
        Resolution: Fixed

> Ensure RMProxy events are processed in-order
> --------------------------------------------
>
>                 Key: YUNIKORN-2329
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2329
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: core - common
>            Reporter: Yu-Lin Chen
>            Assignee: Yu-Lin Chen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>         Attachments: [YUNIKORN-2329] Benchmark Result.png
>
>
> As a solution to the racing issue in YUNIKORN-2327, we can remove the goroutines in [RMProxy.UpdateNode()|https://github.com/apache/yunikorn-core/blob/master/pkg/rmproxy/rmproxy.go#L378-L389] (and UpdateApplication/UpdateAllocation) to make sure the function put si.NodeRequest in channel in the same order from shim.  Perforamance benchmarking must be done before applying this change.



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