> Attached image is generated by htrace-hbase (fixed for hbase-1).
You can see the image here...
http://iwasakims.github.io/images/end2end-create-table.png
I could not expected result for put and scan.
http://iwasakims.github.io/images/tracing-put.png
http://iwasakims.github.io/images/tracing-s
I got expected end-to-end trace at least for creating hbase table by
htrace-3.1.0-incubating.
Attached image is generated by htrace-hbase (fixed for hbase-1).
On 2/27/15 06:15, Masatake Iwasaki wrote:
> The double-detach should be fixed in HBase as well.
I got HDFS tracing spans originated by
> The double-detach should be fixed in HBase as well.
I got HDFS tracing spans originated by HBase operation
with htrace-3.2.0-SNAPSHOT (with HTRACE-119)
but there seems to be the case that span is not closed in HBase.
I did not get RuntimeException due to double detach/close (by HTRACE-101).
O
The double-detach should be fixed in HBase as well.
On Thu, Feb 26, 2015 at 1:07 AM, Masatake Iwasaki <
iwasak...@oss.nttdata.co.jp> wrote:
> > perhaps a double detach.
>
> It turned out to be double detach of NullScope singleton and I filed
> HTRACE-119.
> I got the error on meta assignments on
> perhaps a double detach.
It turned out to be double detach of NullScope singleton and I filed
HTRACE-119.
I got the error on meta assignments on regionserver startup without
starting trace spans..
Thanks,
Masatake
On 2/26/15 09:58, Colin P. McCabe wrote:
Hmm. Looking at that error, my gu
Hmm. Looking at that error, my guess would be that there is an
incorrect usage of TraceScope#detach going on somewhere in hbase...
perhaps a double detach. But I could be wrong. We added some code
recently to catch issues like this.
best,
Colin
On Wed, Feb 25, 2015 at 12:28 AM, Masatake Iwasak
I tried hbase-1 built against today's htrace-3.2.0-SNAPSHOT (with quick
fix to TestHTraceHooks).
I got the error below in regionserver log.
I will dig this tomorrow.::
2015-02-25 00:18:29,270 ERROR [RS_OPEN_META-centos7:16201-0]
htrace.Tracer: Tried to detach trace span null but it has alread
Thanks for trying this, Mastake. I've got HDFS working on my cluster
with tracing and LocalFileSpanReceiver. Did you try using HBase +
HDFS with LocalFileSpanReceiver? Be sure to use a build including
HTRACE-112 since LFSR was kind of busted prior to that.
I'm going to do a longer writeup about
Hi,
Thanks for trying this. I am sorry for late reply.
I tried this today
by hbase-1.0.1-SANPSHOT built with {{-Dhadoop-two.version=2.7.0-SNAPSHOT}}
in pseudo distributed cluster
but failed to get end-to-end trace.
I checked that
* tracing works for both of hbase and hdfs,
* hbase runs with 2.7
On Thu, Feb 12, 2015 at 1:23 PM, Chunxu Tang wrote:
> Hi all,
>
> Thanks for your detailed replies!
>
> Now I have tested end-to-end tracing in two versions of HBase (0.98.10 and
> 0.99.2), combined with Hadoop 2.6.0 and htrace-master (3.0.4), and both of
> them failed. For HBase 0.98.10, it actua
Hi all,
Thanks for your detailed replies!
Now I have tested end-to-end tracing in two versions of HBase (0.98.10 and
0.99.2), combined with Hadoop 2.6.0 and htrace-master (3.0.4), and both of
them failed. For HBase 0.98.10, it actually has htrace 2.0.4 core, so it's
normal to get no traces. While
No, I think I'm the one who's missing something. :)
I will give that a try next time I'm testing out end-to-end tracing.
thanks guys.
Colin
On Wed, Feb 11, 2015 at 4:36 PM, Enis Söztutar wrote:
> mvn install just installs it in local cache which you can then use for
> building other projects. S
mvn install just installs it in local cache which you can then use for
building other projects. So no need to have to define a file based local
repo. Am I missing something?
Enis
On Wed, Feb 11, 2015 at 12:36 PM, Nick Dimiduk wrote:
> Oh, I see. I was assuming a local build of Hadoop snapshot i
Oh, I see. I was assuming a local build of Hadoop snapshot installed into
the local cache.
On Wednesday, February 11, 2015, Colin P. McCabe wrote:
> On Wed, Feb 11, 2015 at 11:27 AM, Nick Dimiduk > wrote:
> > I don't recall the hadoop release repo restriction being a problem, but I
> > haven't
On Wed, Feb 11, 2015 at 11:27 AM, Nick Dimiduk wrote:
> I don't recall the hadoop release repo restriction being a problem, but I
> haven't tested it lately. See if you can just specify the release version
> with -Dhadoop.version or -Dhadoop-two.version.
>
Sorry, it's been a while since I did thi
I don't recall the hadoop release repo restriction being a problem, but I
haven't tested it lately. See if you can just specify the release version
with -Dhadoop.version or -Dhadoop-two.version.
I would go against branch-1.0 as this will be the eminent 1.0.0 release and
had HTrace 3.1.0-incubating
Thanks for trying stuff out! Sorry that this is a little difficult at
the moment.
To really do this right, you would want to be using Hadoop with HTrace
3.1.0, and HBase with HTrace 3.1.0. Unfortunately, there hasn't been
a new release of Hadoop with HTrace 3.1.0. The only existing releases
of
Hi Joshua,
In theory there's nothing special for you to do. Just issue your query to
HBase with tracing enabled. The active span will go through HBase, down
into HDFS, and back again. You'll need both systems collecting spans into
the same place so that you can report on the complete trace tree.
Hi all,
Now I’m exploiting HTrace to trace request level data flows in HBase and
HDFS. I have successfully traced HBase and HDFS by using HTrace,
respectively.
After that, I combine HBase and HDFS together and I want to just send a
PUT/GET request to HBase, but to trace the whole data flow in bot
19 matches
Mail list logo
