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

Bogdan Drutu commented on HADOOP-15566:
---------------------------------------

[~elek] - I have some questions about OT integration:

1) What implementation will be shipped with the official HBase binary?

2) How can somebody use a different implementation?

3) How do you ensure that a different implementation (that is not tested with 
your entire test suite) may not corrupt user data? I think it is very important 
that all the tests are running with the implementation that user uses in 
production.

FYI: I know I am biased but I think that a different approach is better here, 
use one implementation (pick something that you like the most) and export these 
data to an configurable endpoint. Then every vendor can consume that format.

 

> 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
>              Labels: security
>         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]

Reply via email to