You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Janus Chow (Jira)" <ji...@apache.org> on 2022/04/05 08:17:00 UTC

[jira] [Resolved] (HDDS-6550) Change log level for exceptions in S3gateway

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

Janus Chow resolved HDDS-6550.
------------------------------
    Release Note: Already fixed. 
      Resolution: Won't Fix

> Change log level for exceptions in S3gateway 
> ---------------------------------------------
>
>                 Key: HDDS-6550
>                 URL: https://issues.apache.org/jira/browse/HDDS-6550
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Janus Chow
>            Assignee: Janus Chow
>            Priority: Major
>              Labels: pull-request-available
>
> In a production cluster, the log level is usually not set to DEBUG, due to the log flushing.
> In S3gateway, some exceptions are logged at DEBUG level, which causes the exception not being able to be shown at first place, we need to restart the service and reconfigure the log level, and after the fix the exception, we need to restart the service and set back the log level.
> This ticket is to change the log level to ERROR instead of DEBUG to easily find the exception.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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