You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2023/12/01 12:34:00 UTC
[jira] [Created] (YUNIKORN-2223) Task: eliminate separate mutex variable
Peter Bacsko created YUNIKORN-2223:
--------------------------------------
Summary: Task: eliminate separate mutex variable
Key: YUNIKORN-2223
URL: https://issues.apache.org/jira/browse/YUNIKORN-2223
Project: Apache YuniKorn
Issue Type: Improvement
Components: shim - kubernetes
Reporter: Peter Bacsko
In {{{}cache.Task{}}}, the lock variable is defined as:
{noformat}
type Task struct {
...
schedulingState TaskSchedulingState
sm *fsm.FSM
lock *sync.RWMutex
} {noformat}
In other parts of the code, we simply embed {{sync.RWMutex}}. There's no need to have a separate variable. Locking and unlocking become simpler.
--
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