accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Keith Turner <ke...@deenlo.com>
Subject Re: tserver.readahead.concurrent.max set to 64 but only running 32 at most.
Date Fri, 17 May 2013 17:10:47 GMT
On Thu, May 16, 2013 at 2:14 PM, David Medinets <david.medinets@gmail.com>wrote:

> Thanks. I double-checked our system by running config in the shell (as
> opposed looking in the configuration file). The config command reported a
> 'system' override of 32. So that explains the limit that I saw. I'm not
> sure where that 'system' override came from.
>

Thats coming from a system config set in the shell, which is stored in
zookeeper.


>
>
> On Thu, May 16, 2013 at 1:25 PM, Eric Newton <eric.newton@gmail.com>
> wrote:
>
> > tserver.scan.files.open.max
> >
> >
> >
> > On Wed, May 15, 2013 at 4:44 PM, David Medinets <
> david.medinets@gmail.com
> > >wrote:
> >
> > > When tserver.readahead.concurrent.max was set to its default setting,
> the
> > > load on our tservers was fairly low. So I changed accumulo-site.xml so
> > the
> > > max is 64. (Go for the gusto!) Then restarted the tservers to ensure
> the
> > > change was picked up.
> > >
> > > New queries are now running 32 concurrent scans on each server with
> > several
> > > scans waiting in the queue. Is there some other accumulo parameter
> that I
> > > need to set to get more than 32 concurrent scans? Is something else
> > > affecting the scans?
> > >
> >
>

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