This is an automated email from the ASF dual-hosted git repository.
ccondit 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 b801a1af56 [YUNIKORN-2041] Update set log level doc (#357)
b801a1af56 is described below
commit b801a1af56e6889c88fd80732888bcfb07ca7c1a
Author: brandboat <[email protected]>
AuthorDate: Thu Oct 26 11:40:18 2023 -0500
[YUNIKORN-2041] Update set log level doc (#357)
Closes: #357
Signed-off-by: Craig Condit <[email protected]>
---
docs/user_guide/troubleshooting.md | 60 +++++++++++++-------------------------
1 file changed, 20 insertions(+), 40 deletions(-)
diff --git a/docs/user_guide/troubleshooting.md
b/docs/user_guide/troubleshooting.md
index 9edbaa7cc0..6662079f0f 100644
--- a/docs/user_guide/troubleshooting.md
+++ b/docs/user_guide/troubleshooting.md
@@ -45,56 +45,36 @@ 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.
-:::`
-
-Stop the scheduler:
-
-```shell script
-kubectl scale deployment yunikorn-scheduler -n yunikorn --replicas=0
-```
-edit the deployment config in vim:
+Edit the yunikorn-configs configmap:
```shell script
-kubectl edit deployment yunikorn-scheduler -n yunikorn
+kubectl edit configmap/yunikorn-configs -n yunikorn
```
-add `LOG_LEVEL` to the `env` field of the container template. For example
setting `LOG_LEVEL` to `0` sets the logging
-level to `INFO`.
+Add `log.level` to the `data` field of the configmap. For example setting
`log.level` to `DEBUG` sets the logging
+level to `DEBUG`.
```yaml
-apiVersion: extensions/v1beta1
-kind: Deployment
+apiVersion: v1
+data:
+ log.level: DEBUG
+ ...
+kind: ConfigMap
metadata:
- ...
-spec:
- template:
...
- spec:
- containers:
- - env:
- - name: LOG_LEVEL
- value: '0'
-```
-
-Start the scheduler:
-
-```shell script
-kubectl scale deployment yunikorn-scheduler -n yunikorn --replicas=1
```
-Available logging levels:
-
-| Value | Logging Level |
-|:-----: |:-------------: |
-| -1 | DEBUG |
-| 0 | INFO |
-| 1 | WARN |
-| 2 | ERROR |
-| 3 | DPanic |
-| 4 | Panic |
-| 5 | Fatal |
+The `log.level` value can be either numeric (-1 through 5) or textual (DEBUG
through FATAL).
+
+| Value | Logging Level |
+|:------:|:-------------:|
+| -1 | DEBUG |
+| 0 | INFO |
+| 1 | WARN |
+| 2 | ERROR |
+| 3 | DPANIC |
+| 4 | PANIC |
+| 5 | FATAL |
## Pods are stuck at Pending state
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
