[HDDS-7124] Setting logLevel through om logLevel endpoint broken - ASF JIRA

Log work

Agile Board

Rank to Top

Rank to Bottom

Attach files

Attach Screenshot

Bulk Copy Attachments

Bulk Move Attachments

Voters

Watch issue

Watchers

Create sub-task

Convert to sub-task

Link

Clone

Labels

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Duplicate
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
None

Description

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.

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