This is an automated email from the ASF dual-hosted git repository.
yuteng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git
The following commit(s) were added to refs/heads/master by this push:
new 173e77ba1 [YUNIKORN-1602] Update text in Set Logging level for
troubleshooting guide (#279)
173e77ba1 is described below
commit 173e77ba1003b89bf77494c5f27cb26dc1d999a7
Author: twilight-SL <[email protected]>
AuthorDate: Wed Mar 8 18:32:55 2023 +0800
[YUNIKORN-1602] Update text in Set Logging level for troubleshooting guide
(#279)
---
docs/user_guide/troubleshooting.md | 4 ++--
versioned_docs/version-1.2.0/user_guide/troubleshooting.md | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/user_guide/troubleshooting.md
b/docs/user_guide/troubleshooting.md
index 9da841852..9edbaa7cc 100644
--- a/docs/user_guide/troubleshooting.md
+++ b/docs/user_guide/troubleshooting.md
@@ -46,8 +46,8 @@ The recommended setup is to leverage
[fluentd](https://www.fluentd.org/) to coll
### Set Logging Level
:::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.
-:::
+We recommend altering the log level via REST API call as this way we don't
need to restart the scheduler pod every time.
+:::`
Stop the scheduler:
diff --git a/versioned_docs/version-1.2.0/user_guide/troubleshooting.md
b/versioned_docs/version-1.2.0/user_guide/troubleshooting.md
index 9da841852..e7afc67bb 100644
--- a/versioned_docs/version-1.2.0/user_guide/troubleshooting.md
+++ b/versioned_docs/version-1.2.0/user_guide/troubleshooting.md
@@ -46,7 +46,7 @@ The recommended setup is to leverage
[fluentd](https://www.fluentd.org/) to coll
### Set Logging Level
:::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.
+We recommend altering the log level via REST API call as this way we don't
need to restart the scheduler pod every time.
:::
Stop the scheduler:
