You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2019/10/25 16:59:00 UTC
[jira] [Reopened] (HDDS-2206) Separate handling for OMException and
IOException in the Ozone Manager
[ https://issues.apache.org/jira/browse/HDDS-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal reopened HDDS-2206:
---------------------------------
Reverted this based on offline conversation with [~aengineer].
Anu has requested we add a config key to control this behavior.
> Separate handling for OMException and IOException in the Ozone Manager
> ----------------------------------------------------------------------
>
> Key: HDDS-2206
> URL: https://issues.apache.org/jira/browse/HDDS-2206
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Manager
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org