[ 
https://issues.apache.org/jira/browse/YUNIKORN-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Craig Condit closed YUNIKORN-2648.
----------------------------------
    Target Version:   (was: 1.6.0)
        Resolution: Won't Do

Closing this as it's not something we can do safely.

> Add deadlock detection config to the configmap
> ----------------------------------------------
>
>                 Key: YUNIKORN-2648
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2648
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - common
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Hsien-Cheng(Ryan) Huang
>            Priority: Critical
>
> The current deadlock detection is configured using environment variables. 
> That requires a change of the image and a restart of the scheduler to take 
> effect and is not easy to maintain.
> We should be using yunikorn-defaults config map for the settings. We want a 
> default set, turned off, for production use cases. However making the configs 
> loadable from the config map makes turning it on easier.
> Update the configmap and restart the scheduler to turn the detection on or 
> off.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org

Reply via email to