You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Chen Yu Teng (Jira)" <ji...@apache.org> on 2023/03/08 10:42:00 UTC
[jira] [Resolved] (YUNIKORN-1602) Update text in Set Logging level for troubleshooting guide
[ https://issues.apache.org/jira/browse/YUNIKORN-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chen Yu Teng resolved YUNIKORN-1602.
------------------------------------
Resolution: Fixed
> Update text in Set Logging level for troubleshooting guide
> ----------------------------------------------------------
>
> Key: YUNIKORN-1602
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1602
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: documentation
> Affects Versions: 1.2.0
> Reporter: Wilfred Spiegelenburg
> Assignee: Lai Yu Chen
> Priority: Major
> Labels: newbie, pull-request-available
>
> The troubleshooting guide states that we require a restart for the log level change through the configuration:
>
> {code:java}
> NOTE
> We recommend altering the log level via REST API call as this way we don't need to restart the scheduler pod every time. But changing the logging level via editing the deployment config requires a restart of the scheduler pod and it's not highly recommended.
> {code}
> That is no longer true after the update of the configuration to v2. We read settings from the config map and we apply the change. The log level should be picked up without restart.
>
--
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