[
https://issues.apache.org/jira/browse/HDDS-2206?focusedWorklogId=327616&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-327616
]
ASF GitHub Bot logged work on HDDS-2206:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Oct/19 05:41
Start Date: 14/Oct/19 05:41
Worklog Time Spent: 10m
Work Description: supratimdeka commented on pull request #12: HDDS-2206.
Separate handling for OMException and IOException in the Ozone Manager.
Contributed by Supratim Deka
URL: https://github.com/apache/hadoop-ozone/pull/12
https://issues.apache.org/jira/browse/HDDS-2206
Introduced a boolean config parameter to control exception propagation from
OM to Clients.
If set to true, all system exceptions (IOException) are thrown as
ServiceException to RPC client - this also propagates the complete server-side
stack trace to the client. If false, system exception stack trace is logged
locally on the server, not sent to client.
The default value is set to true for now. For Ozone GA, we can revisit this
choice.
Business Exception (OMException) handling is not changed.
This change does not include propagation of exceptions from within Ratis
server.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 327616)
Time Spent: 1.5h (was: 1h 20m)
> 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
> Time Spent: 1.5h
> 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
