[
https://issues.apache.org/jira/browse/YUNIKORN-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikandan R updated YUNIKORN-1116:
-----------------------------------
Description:
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
was:
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
> Update SchedulerNode properties using proper locks
> --------------------------------------------------
>
> Key: YUNIKORN-1116
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1116
> Project: Apache YuniKorn
> Issue Type: Bug
> Reporter: Manikandan R
> Assignee: Manikandan R
> Priority: Major
> 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: [email protected]
For additional commands, e-mail: [email protected]
