[
https://issues.apache.org/jira/browse/YUNIKORN-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit resolved YUNIKORN-2539.
------------------------------------
Resolution: Fixed
> Add optional deadlock detection
> -------------------------------
>
> Key: YUNIKORN-2539
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2539
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler, shim - kubernetes
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0, 1.5.1
>
>
> We make heavy use of sync.Mutex and sync.RWMutex in our code. Unfortunately,
> while these are very performant, they can lead to difficult-to-diagnose
> deadlocks.
> If we substitute our own locking routines, we can optionally enable deadlock
> detection. See [https://github.com/sasha-s/go-deadlock] for a possible
> solution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
