[jira] [Commented] (HBASE-18601) Remove Htrace 3.2

["stack (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-18601:
-------------------------------

Above cited discussion up on dev@htrace has died down. If I were to summarize, it would be that htrace is near death but not just yet; lets give it one more go. In particular, let the proofing project be hooking up hbase and hdfs (and ycsb even since it has trace too).

Meantime, lets upgrade our htrace internally. Will assign [~tamaas] to have a go at it (hope you don't mind my reassign [~andrew.purtell@gmail.com]). This issue is about updating lib only. Not about telling a good trace story. That we can do later.

[~tamaas] You saw HBASE-14451 ? It has a bunch of updating going on. It was unfinished. Might be of some use to you sir.

> Remove Htrace 3.2
> -----------------
>
>                 Key: HBASE-18601
>                 URL: https://issues.apache.org/jira/browse/HBASE-18601
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 2.0.0, 3.0.0
>            Reporter: Tamas Penzes
>            Assignee: Andrew Purtell
>             Fix For: 2.0.0-alpha-3
>
>         Attachments: HBASE-18601.master.001.patch
>
>
> HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy, the upgrade to 4.x is not trivial and would take time. It might not worth to keep it in this state, so would be better to remove it.
> Of course it doesn't mean tracing would be useless, just that in this form the use of HTrace 3.2 might not add any value to the project and fixing it would be far too much effort.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)