[
https://issues.apache.org/jira/browse/HDDS-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046056#comment-18046056
]
ASF GitHub Bot commented on HDDS-2206:
--------------------------------------
github-actions[bot] commented on PR #1637:
URL: https://github.com/apache/hadoop/pull/1637#issuecomment-3667684462
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> Separate handling for OMException and IOException in the Ozone Manager
> ----------------------------------------------------------------------
>
> Key: HDDS-2206
> URL: https://issues.apache.org/jira/browse/HDDS-2206
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Manager
> Reporter: Supratim Deka
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> As part of improving error propagation from the OM for ease of
> troubleshooting and diagnosis, the proposal is to handle IOExceptions
> separately from the business exceptions which are thrown as OMExceptions.
> Handling for OMExceptions will not be changed in this jira.
> Handling for IOExceptions will include logging the stacktrace on the server,
> and propagation to the client under the control of a config parameter.
> Similar handling is also proposed for SCMException.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
