[ 
https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey reopened HBASE-18601:
---------------------------------

{{TestHTraceHooks}} fails reliably in master (nightly and on my local box) and 
passes if I revert this change.

I tried digging in to see why the failure. It looks like before the patch this 
part of the test checked for 1 root instead of 3. There's not enough detail in 
the test for it to be obvious how many roots ought to be there. Unfortunately, 
the relevant class, {{TraceTree}}, isn't in the [HTrace 4.1 
javadocs|http://htrace.incubator.apache.org/javadoc/4.1/htrace-core/index.html] 
and the [HTrace website|http://htrace.incubator.apache.org/#releases] makes no 
references at all to a 4.2 release. So I'm at a loss.

> Update Htrace to 4.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: Balazs Meszaros
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-18601.master.001.patch, 
> HBASE-18601.master.002.patch, HBASE-18601.master.003 (3).patch, 
> HBASE-18601.master.003.patch, HBASE-18601.master.004.patch, 
> HBASE-18601.master.004.patch, HBASE-18601.master.005.patch, 
> HBASE-18601.master.006.patch, HBASE-18601.master.006.patch, 
> HBASE-18601.master.007.patch, HBASE-18601.master.007.patch, 
> HBASE-18601.master.007.patch, HBASE-18601.master.008.patch, 
> HBASE-18601.master.009.patch, HBASE-18601.master.009.patch, 
> HBASE-18601.master.010.patch, HBASE-18601.master.010.patch, 
> HBASE-18601.master.011.patch, HBASE-18601.master.012.patch, 
> HBASE-18601.master.013.patch, HBASE-18601.master.014.patch, 
> HBASE-18601.master.014.patch, HBASE-18601.master.015.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.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Based on the decision of the community we keep htrace now and update version



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

Reply via email to