[
https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534634#comment-16534634
]
Steve Loughran commented on HADOOP-15566:
-----------------------------------------
Nice screenshots
* The HDFS team need to be involved in all discussions w.r.t tracing and wire
protocols; I see Anu is watching; [~jnp] should keep an eye on it too
* And hbase, eg @stack.
I don't see the existing field being reusable unless there's no risk that an
htrace client -> opentrace server or opentrace client to htrace-enabled server
isn't going to do bad things. Even if we don't know of anything in production,
it's part of our [compatibility
definition|http://hadoop.apache.org/docs/r3.0.3/hadoop-project-dist/hadoop-common/Compatibility.html#Wire_Protocols].
Making it a new optional field & ignoring the htrace one is the safe route.
> 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,
> ss-trace-s3a.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
