[
https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530226#comment-16530226
]
Steve Loughran commented on HADOOP-15566:
-----------------------------------------
bq. we'll need to update client -> namenode RPC messages, as well as client ->
datanode RPC, KMS Rest API. So wire compatibility needs to be considered. (Some
messages already carries htrace trace id. Would it make sense to replace the
htrace trace id field with opentracing trace id field?
if it breaks wire compatibility, unless is a protobuf optional field, it'll be
an incompatible protocol change. If the field is reused, the servers need to
handle the situation of "older client with htrace enabled makes RPC call to
server with opentrace".
> Remove HTrace support
> ---------------------
>
> Key: HADOOP-15566
> URL: https://issues.apache.org/jira/browse/HADOOP-15566
> Project: Hadoop Common
> Issue Type: Improvement
> Components: metrics
> Affects Versions: 3.1.0
> Reporter: Todd Lipcon
> Priority: Major
> Attachments: Screen Shot 2018-06-29 at 11.59.16 AM.png
>
>
> The HTrace incubator project has voted to retire itself and won't be making
> further releases. The Hadoop project currently has various hooks with HTrace.
> It seems in some cases (eg HDFS-13702) these hooks have had measurable
> performance overhead. Given these two factors, I think we should consider
> removing the HTrace integration. If there is someone willing to do the work,
> replacing it with OpenTracing might be a better choice since there is an
> active community.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
