[
https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535828#comment-16535828
]
Ben Sigelman commented on HADOOP-15566:
---------------------------------------
[[email protected]] I agree that a new field (for the tracing context) makes
the most sense from a compatibility standpoint.
[~jojochuang]: are there specific blockers or questions you have about the OT
port? If so, let me know and I'll do my best to address/answer them. I'm also
happy to help with the mechanics of the change (or find someone with more
cycles in the OT community to do the same). This can be a really positive thing
for HDFS, HBase, etc, as the traces within the datastore/filesystem can be
connected to the traces in the application above, regardless of the particular
tracing system in use. (I know that at google, it was valuable for both the
bigtable core team and for bigtable users to see traces that wend their way
from app code into bigtable and back, esp for slow / poorly-constructed
queries).
> 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: [email protected]
For additional commands, e-mail: [email protected]
