Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CADcMMgFXU+s4QBBFfGZTKzpGpPb+6o+4CA2HHVqfDNxdV1uAVg@mail.gmail.com>
References: 
 <CADcMMgFbbwOB5fxiGA0cBVCPzCxVAZuv6Q_hKHCanFyVO4ncyQ@mail.gmail.com>
 <CANZa=GvnrzirJjKMDePNvL0mn1qjqe=iDYA5me3xsZeTaH=ibQ@mail.gmail.com>
 <21843.61664.956285.397408@bfym.cloudera.com>
 <CADcMMgFXU+s4QBBFfGZTKzpGpPb+6o+4CA2HHVqfDNxdV1uAVg@mail.gmail.com>
From: Nick Dimiduk <ndimiduk@gmail.com>
Date: Wed, 13 May 2015 18:04:24 -0700
Message-ID: 
 <CANZa=Gs13p81bVM5GtxhL28DEy18+sChXWGXqFr5Ji1JYTqmYQ@mail.gmail.com>
Subject: Re: New post on hbase-1.1.0 throttling feature up on our Apache blog
To: hbase-user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=f46d043be0ee2e85f605160050b3

--f46d043be0ee2e85f605160050b3
Content-Type: text/plain; charset=UTF-8

Sorry. Yeah, sure, I can ask over there.

The throttle was set by user in these tests.  You cannot directly
> throttle a specific job, but do have the option to set the throttle
> for a table or a namespace.  That might be sufficient for you to
> achieve your objective (unless those jobs are run by one user and
> access the same table.)


Maybe running as different users is the key, but this seems like a very
important use-case to support -- folks doing aggregate analysis
concurrently on an online table.

On Wed, May 13, 2015 at 5:53 PM, Stack <stack@duboce.net> wrote:

> Should we add in your comments on the blog Govind: i.e. the answers to
> Nicks' questions?
> St.Ack
>
> On Wed, May 13, 2015 at 5:48 PM, Govind Kamat <gkamat@cloudera.com> wrote:
>
> >  > This is a great demonstration of these new features, thanks for
> > pointing it
> >  > out Stack.
> >  >
> >  > I'm curious: what percentile latencies are this reported? Does the
> >  > non-throttled user see significant latency improvements in the 95,
> 99pct
> >  > when the competing, scanning users are throttled? MB/s and req/s are
> >  > managed at the region level? Region server level? Aggregate?
> >
> > The latencies reported in the post are average latencies.
> >
> > Yes, the non-throttled user sees an across-the-board improvement in
> > the 95th and 99th percentiles, in addition to the improvement in
> > average latency.  The extent of improvement is significant as well but
> > varies with the throttle pressure, just as in the case of the average
> > latencies.
> >
> > The total throughput numbers (req/s) are aggregate numbers reported by
> > the YCSB client.
> >
> >  > These throttle points are by user? Is there a way for us to say "all
> MR
> >  > jobs are lower priority than online queries"?
> >  >
> >
> > The throttle was set by user in these tests.  You cannot directly
> > throttle a specific job, but do have the option to set the throttle
> > for a table or a namespace.  That might be sufficient for you to
> > achieve your objective (unless those jobs are run by one user and
> > access the same table.)
> >
> > Govind
> >
> >
> >  > Thanks,
> >  > Nick
> >  >
> >  > On Tue, May 12, 2015 at 1:58 PM, Stack <stack@duboce.net> wrote:
> >  >
> >  > > .. by our Govind.
> >  > >
> >  > > See here:
> >  > >
> >
> https://blogs.apache.org/hbase/entry/the_hbase_request_throttling_feature
> >  > >
> >  > > St.Ack
> >  > >
> >
>

--f46d043be0ee2e85f605160050b3--