[
https://issues.apache.org/jira/browse/HDDS-2175?focusedWorklogId=320416&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-320416
]
ASF GitHub Bot logged work on HDDS-2175:
----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Sep/19 09:36
Start Date: 30/Sep/19 09:36
Worklog Time Spent: 10m
Work Description: supratimdeka commented on pull request #1520:
HDDS-2175. Propagate stack trace for OM Exceptions to the Client. Contributed
by Supratim Deka
URL: https://github.com/apache/hadoop/pull/1520
----------------------------------------------------------------
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: 320416)
Time Spent: 1h (was: 50m)
> Propagate System Exceptions from the OzoneManager
> -------------------------------------------------
>
> Key: HDDS-2175
> URL: https://issues.apache.org/jira/browse/HDDS-2175
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: Ozone Manager
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Exceptions encountered while processing requests on the OM are categorized as
> business exceptions and system exceptions. All of the business exceptions are
> captured as OMException and have an associated status code which is returned
> to the client. The handling of these is not going to be changed.
> Currently system exceptions are returned as INTERNAL ERROR to the client with
> a 1 line message string from the exception. The scope of this jira is to
> capture system exceptions and propagate the related information(including the
> complete stack trace) back to the client.
> There are 3 sub-tasks required to achieve this
> 1. Separate capture and handling for OMException and the other
> exceptions(IOException). For system exceptions, use Hadoop IPC
> ServiceException mechanism to send the stack trace to the client.
> 2. track and propagate exceptions inside Ratis OzoneManagerStateMachine and
> propagate up to the OzoneManager layer (on the leader). Currently, these
> exceptions are not being tracked.
> 3. Handle and propagate exceptions from Ratis.
> Will raise jira for each sub-task.
>
--
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
