[
https://issues.apache.org/jira/browse/HDDS-2175?focusedWorklogId=318152&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-318152
]
ASF GitHub Bot logged work on HDDS-2175:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Sep/19 08:56
Start Date: 25/Sep/19 08:56
Worklog Time Spent: 10m
Work Description: elek commented on issue #1520: HDDS-2175. Propagate
stack trace for OM Exceptions to the Client. Contributed by Supratim Deka
URL: https://github.com/apache/hadoop/pull/1520#issuecomment-534923342
Thank you very much to file this issue @supratimdeka. The big question (for
me) is the type of the exceptions.
There are two kind of exception:
* Business exceptions (eg. VolumeNotFound) and
* System exceptions (eg. connection refused).
This particular code is about propagating the business exceptions. I am not
sure if we need to
propagate the strack trace there. For example a VOLUME_NOT_FOUND doesn't
require any exception message to be propagated.
It's enough to propagate the error type and the message. (This is what we
do.)
In case of a real system exception the stack trace is is propagated with
Hadoop RPC (inside an RpcException If I remember well... The full stack trace
is propagated there...)
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 318152)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
