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 "Elek, Marton (JIRA)" <ji...@apache.org> on 2019/03/13 12:16:00 UTC

[jira] [Created] (HDDS-1258) Fix error propagation for SCM protocol

Elek, Marton created HDDS-1258:
----------------------------------

             Summary: Fix error propagation for SCM protocol
                 Key: HDDS-1258
                 URL: https://issues.apache.org/jira/browse/HDDS-1258
             Project: Hadoop Distributed Data Store
          Issue Type: Improvement
            Reporter: Elek, Marton
            Assignee: Kitti Nanasi


HDDS-1068 fixed the error propagation between the OM client and OM server.

By default the Server.java transforms all the IOExceptions to one string (message + stack trace) and this is returned to the client.

But for business exception (eg. volume not found, chill mode is active, etc.) this is not what we need.

In the OM side we fixed this behaviour. In the ServerSideTranslator classes we catch (server) the business (OMException) exceptions and serialize them to the response object.

The exception (and the status code) is stored in message/status field of the OMResponse (hadoop-ozone/common/src/main/proto/OzoneManagerProtocol.proto)

Here I propose to do the same for the ScmBlockLocationProtocol.proto.

Unfortunately there is no common parent object (like OMRequest) in this protocol, but we can easily add one as only the Serverside/Clientside translator should be changed for that. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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