You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2022/11/28 05:38:00 UTC

[jira] [Commented] (YUNIKORN-1418) Add scheduler state dump to Trouble Shooting page

    [ https://issues.apache.org/jira/browse/YUNIKORN-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17639796#comment-17639796 ] 

Wilfred Spiegelenburg commented on YUNIKORN-1418:
-------------------------------------------------

I just re-read the page for troubleshooting again and it says: "restart the scheduler for changing the log level".

That should be fixed also, we have the REST call to change the log level and we can do it on the fly...

> Add scheduler state dump to Trouble Shooting page 
> --------------------------------------------------
>
>                 Key: YUNIKORN-1418
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1418
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Jagadeesan A S
>            Priority: Minor
>              Labels: newbie
>
> An important tool to use during trouble shooting is the state dump.
> https://yunikorn.apache.org/docs/next/api/scheduler#retrieve-full-state-dump
> Collecting a state dump is not mentioned as part of the troubleshooting page and should be added.
> We also should add that restarting the scheduler should be a last resort action to get going again and should never be performed before all logs and state dump are collected.



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

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