hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jeff saremi <jeffsar...@hotmail.com>
Subject Re: Need guidance on getting detailed elapsed times in every stage of processing a request
Date Thu, 02 Mar 2017 22:26:13 GMT
So i'd like to come back to my original question on how to get about separating the latency
of HDFS from HBase.

Is there a most appropriate log4j TRACE option that could print out this information to the
logs?
Thanks

________________________________
From: jeff saremi <jeffsaremi@hotmail.com>
Sent: Thursday, March 2, 2017 12:45:59 PM
To: Hbase-User
Subject: Re: Need guidance on getting detailed elapsed times in every stage of processing
a request

Thanks so much for the advice! Looking forward to when Tracing gets picked up again

________________________________
From: saint.ack@gmail.com <saint.ack@gmail.com> on behalf of Stack <stack@duboce.net>
Sent: Thursday, March 2, 2017 12:17:35 PM
To: Hbase-User
Subject: Re: Need guidance on getting detailed elapsed times in every stage of processing
a request

HBase/HTrace integration once worked but has long since rotted.
Refactorings of internals without proper respect for trace connections is
the main culprit. Updates in htrace and hdfs that need attention
reconnecting spans, etc., is another. On top of this, zipkin project has
seen a burst of effort of late that would seem to offer much promise if
someone of us spent some time rejiggering how HTrace and Zipkin relate.

I would not waste any time on trying to setup HTrace for HBase at least
until after HBASE-14451 goes in, an issue that has been put aside with a
while now. Sorry if you've burned time on this to date.

Yours,
St.Ack

On Thu, Mar 2, 2017 at 6:28 AM, jeff saremi <jeffsaremi@hotmail.com> wrote:

> Where would i seek help for issues revolving around HTrace and zipkin?
> Here? Because I have configured everything the way documentation said but i
> see nothing in the zipkin server or in the logs. nothing at all
>
> ________________________________
> From: jeff saremi <jeffsaremi@hotmail.com>
> Sent: Tuesday, February 28, 2017 12:52:32 PM
> To: user@hbase.apache.org
> Subject: Re: Need guidance on getting detailed elapsed times in every
> stage of processing a request
>
> No I had not. but it looks like what i needed. Thanks Ted.
>
> I'll see if I have any more questions after reading this.
>
> ________________________________
> From: Ted Yu <yuzhihong@gmail.com>
> Sent: Tuesday, February 28, 2017 12:47:08 PM
> To: user@hbase.apache.org
> Subject: Re: Need guidance on getting detailed elapsed times in every
> stage of processing a request
>
> Have you looked at:
> http://hbase.apache.org/book.html#tracing
>
> On Tue, Feb 28, 2017 at 12:37 PM, jeff saremi <jeffsaremi@hotmail.com>
> wrote:
>
> > I think we need to get detailed information from HBase RegionServer logs
> > on how a request (read or write) is processed. Specifically speaking, i
> > need to know of say 100 ms time spent in processing a write, how much of
> it
> > was spent waiting for the HDFS?
> > What is the most efficient way of enabling this in log4j properties? Are
> > there better mechanisms to get this information?
> >
> > If I can get this in the log, then I can process the logs offline or in
> > neartime and mount some dashboards on the top.
> >
> > thanks
> >
> >
> > Jeff
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message