[ https://issues.apache.org/jira/browse/HDDS-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938148#comment-16938148 ]
Hudson commented on HDDS-2067: ------------------------------ FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17388 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/17388/]) HDDS-2067. Create generic service facade with tracing/metrics/logging (aengineer: rev f647185905f6047fc9734b8aa37d6ef59b6082c2) * (add) hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/server/OzoneProtocolMessageDispatcher.java * (add) hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/protocol/package-info.java * (add) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/function/FunctionWithServiceException.java * (edit) hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/server/TestSCMBlockProtocolServer.java * (add) hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/protocol/StorageContainerLocationProtocolServerSideTranslatorPB.java * (edit) hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/server/SCMClientProtocolServer.java * (delete) hadoop-hdds/common/src/main/java/org/apache/hadoop/ozone/protocolPB/StorageContainerLocationProtocolServerSideTranslatorPB.java * (edit) hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/protocolPB/OzoneManagerProtocolServerSideTranslatorPB.java * (edit) hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/server/SCMBlockProtocolServer.java * (delete) hadoop-hdds/common/src/main/java/org/apache/hadoop/ozone/protocolPB/ScmBlockLocationProtocolServerSideTranslatorPB.java * (add) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/function/package-info.java * (add) hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/protocol/ScmBlockLocationProtocolServerSideTranslatorPB.java * (edit) hadoop-ozone/insight/src/main/java/org/apache/hadoop/ozone/insight/scm/ScmProtocolBlockLocationInsight.java > Create generic service facade with tracing/metrics/logging support > ------------------------------------------------------------------ > > Key: HDDS-2067 > URL: https://issues.apache.org/jira/browse/HDDS-2067 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Reporter: Marton Elek > Assignee: Marton Elek > Priority: Major > Labels: pull-request-available > Fix For: 0.5.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > We started to use a message based GRPC approach. Wen have only one method and > the requests are routed based on a "type" field in the proto message. > For example in OM protocol: > {code} > /** > The OM service that takes care of Ozone namespace. > */ > service OzoneManagerService { > // A client-to-OM RPC to send client requests to OM Ratis server > rpc submitRequest(OMRequest) > returns(OMResponse); > } > {code} > And > {code} > message OMRequest { > required Type cmdType = 1; // Type of the command > ... > {code} > This approach makes it possible to use the same code to process incoming > messages in the server side. > ScmBlockLocationProtocolServerSideTranslatorPB.send method contains the logic > of: > * Logging the request/response message (can be displayed with ozone insight) > * Updated metrics > * Handle open tracing context propagation. > These functions are generic. For example > OzoneManagerProtocolServerSideTranslatorPB use the same (=similar) code. > The goal in this jira is to provide a generic utility and move the common > code for tracing/request logging/response logging/metrics calculation to a > common utility which can be used from all the ServerSide translators. -- 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