hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Supratim Deka (Jira)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-2175) Propagate stack trace for OM Exceptions to the Client
Date Fri, 27 Sep 2019 11:33:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Supratim Deka updated HDDS-2175:
--------------------------------
    Description: 
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 Exceptions from Ratis and report 
  


  was:
Ozone Manager responds with a Status code and the summary message when an exception occurs
while running the OM request handlers.

The proposal is to respond to the client with the complete stack trace for the exception,
as part of the response message.

This makes debugging more convenient without requiring code change on the client, because
the status code is retained in the response message.




> Propagate stack trace for OM Exceptions to the Client
> -----------------------------------------------------
>
>                 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: 50m
>  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 Exceptions from Ratis and report 
>   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message