[jira] [Resolved] (HDDS-7124) Setting logLevel through om logLevel endpoint broken

["Attila Doroszlai (Jira)" <ji...@apache.org>]

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

Attila Doroszlai resolved HDDS-7124.
------------------------------------
    Resolution: Fixed

> Setting logLevel through om logLevel endpoint broken 
> -----------------------------------------------------
>
>                 Key: HDDS-7124
>                 URL: https://issues.apache.org/jira/browse/HDDS-7124
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Neil Joshi
>            Priority: Major
>         Attachments: figure1-om-logLevel-problem.png, figure2a-s3g-noproblem.png
>
>
> Previously, we could set the log level for an ozone manager class through the ozone manager endpoint, localhost:9874/logLevel for any class.  Recently that has changed and results in an error returned to the user: *_Sorry, class org.apache.commons.logging.impl.SLF4JLocationAwareLog not supported._* 
> see attached figure1-om-logLevel-problem.
> !figure1-om-logLevel-problem.png!
> This also appears to affect the ozone daemonlog shell command as well with the user informed the level is being set, however the level does not change as it appears to be set through the same endpoint.
>  
> This problem however, does not affect the logLevel set through the s3gateway endpoint, localhost:9878/logLevel.  Getting and setting log levels through this endpoint appears unaffected.  It gives a user a message indicating the log class used is: Log Class: *_org.apache.commons.logging.impl.Log4JLogger_*
> see attached figure2-s3g-noproblem
> !figure2a-s3g-noproblem.png!
>  
>  



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

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