[
https://issues.apache.org/jira/browse/HDDS-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duong updated HDDS-6905:
------------------------
Description:
Most of the time, OMException is left unhandled and that results in errors
logs in S3G log. In many cases, OMException indicates customer related event,
e.g. invalid parameters, permission, or vol/bucket/object not found.
A OMException handler need to be implemented to handle all OMException and
decide when it needs logging in S2G log.
was:
Most of the time, OMException is left unhandled and that results in errors
logs in S3G
This ticket includes the effort to decide, in the mentioned exception handler,
which exceptions need logging in S3G log.
E.g. OMExceptions which are mapped to 4xx doesn't need to be in S3G log, and
should be sent to Audit log already.
> Correct logging unhandled OMException in S3G log
> ------------------------------------------------
>
> Key: HDDS-6905
> URL: https://issues.apache.org/jira/browse/HDDS-6905
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: S3
> Reporter: Duong
> Priority: Major
>
> Most of the time, OMException is left unhandled and that results in errors
> logs in S3G log. In many cases, OMException indicates customer related event,
> e.g. invalid parameters, permission, or vol/bucket/object not found.
> A OMException handler need to be implemented to handle all OMException and
> decide when it needs logging in S2G log.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
