[
https://issues.apache.org/jira/browse/YUNIKORN-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit updated YUNIKORN-2329:
-----------------------------------
Description: 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. (was: As a temporarily
solution before finalizing the solution of the racing issue in YUNIKORN-2327,
we can temporarily remove the goroutine in
[RMProxy.UpdateNode()|https://github.com/apache/yunikorn-core/blob/master/pkg/rmproxy/rmproxy.go#L378-L389]
to make sure the function put si.NodeRequest in channel in the same order from
shim. Perforamcne benchmarking must be done before applying this change.
We should revert this change when applying the final solution.)
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
