[
https://issues.apache.org/jira/browse/HBASE-14451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901401#comment-14901401
]
stack commented on HBASE-14451:
-------------------------------
@enis That is right. They are incompatible. For the hbase trace to be able to
continue through hdfs, the versions need to align. Same for dumping Spans from
a process to a SpanReceiver, the versions need to align; their RPC is
incompatible. This patch makes it so we can trace hbase with htrace 4.0. When
the trace hits an hdfs that is instrumented with htrace 3.x, it will not be
able to progress; hdfs will show as a hole. htrace 4.0.0 and htrace 3.2.0 can
both be on the CLASSPATH and will not clash.
HBase is currently 3.1. HDFS 2.7.1 is also 3.1 (older hbase/hdfs have the
pre-apache-incubator htrace in them). HTrace 3.1 dpes not tell a good tracing
story... dumping into a 3.2 store which should work might get you something but
for sure you can tell a bit of a story when up on 4.0.0.
Not sure when we will have aligned versions in shipping apache hbase and hdfs.
Hopefully can get this patch into 1.2 (since it does not clash with older
versions). Hadoop 2.8 would be first version with 4.0.0 htrace.
> Move on to htrace-4.0.0 (from htrace-3.2.0)
> -------------------------------------------
>
> Key: HBASE-14451
> URL: https://issues.apache.org/jira/browse/HBASE-14451
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Assignee: stack
> Attachments: 14451.txt, 14451v2.txt, 14451v3.txt, 14451v4.txt
>
>
> htrace-4.0.0 was just release with a new API. Get up on it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
