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 2022/04/18 16:25:00 UTC
[jira] [Resolved] (YUNIKORN-1116) Update SchedulerNode properties using proper locks
[ https://issues.apache.org/jira/browse/YUNIKORN-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Condit resolved YUNIKORN-1116.
------------------------------------
Fix Version/s: 1.0.0
Resolution: Fixed
Merged to master and branch-1.0.
> Update SchedulerNode properties using proper locks
> --------------------------------------------------
>
> Key: YUNIKORN-1116
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1116
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> SchedulerNode properties gets updated without having proper lock mechanism in place. For example, {{schedulerNode.occupied = common.Add(schedulerNode.occupied, resource)}} in {{updateNodeOccupiedResources}} method. We should call {{setOccupiedResource}} here.
> Please find out any other places and fix altogether. Please refer the discussion [https://github.com/apache/incubator-yunikorn-k8shim/pull/380#issuecomment-1066328969] for more details
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org