You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2019/01/31 10:09:00 UTC

[jira] [Commented] (RATIS-478) Support custom grpc interceptors

    [ https://issues.apache.org/jira/browse/RATIS-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757090#comment-16757090 ] 

Elek, Marton commented on RATIS-478:
------------------------------------

First version is uploaded. I am thinking how it could be unit tested in a simple way. Let me know if you have ideas.

> Support custom grpc interceptors
> --------------------------------
>
>                 Key: RATIS-478
>                 URL: https://issues.apache.org/jira/browse/RATIS-478
>             Project: Ratis
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>         Attachments: RATIS-478.001.patch
>
>
> While Ratis already has opencencus dependencies the current Ozone tries to use opentracing. (See HDDS-1017). 
> To support opentracing (or any other tracing utility) we need an extension point to add any grpc server/client interceptor. With the interceptor it would be possible to propagate existing tracing context over the wire.
> This patch is a very small modification: if the classname is the interceptor is defined, the interceptor will be added to the client/server side. 



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