Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Message-ID: <56A2848D.8090201@gmail.com>
Date: Fri, 22 Jan 2016 14:35:41 -0500
From: Josh Elser <josh.elser@gmail.com>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: dev@accumulo.apache.org
Subject: Re: question on data block cache
References: <1453306946227-15906.post@n5.nabble.com>
 <CADxc9Bkjvfz3LND6gj_42bNuKkHpmOvLhA5m0YjpB6vjv4-fnw@mail.gmail.com>
 <1453474141992-15925.post@n5.nabble.com>
 <CADxc9B=iG4iU9pksS8UYUea-TEk2vUq5+B3LKUzK8dpfq==4nQ@mail.gmail.com>
 <1453478136795-15927.post@n5.nabble.com>
 <CADxc9Bmk2xf=jWyPkhcr1_0tRrr38ZqwjjL2+4yxuix_c_rygA@mail.gmail.com>
 <1453481134585-15929.post@n5.nabble.com> <56A263A7.5030208@gmail.com>
 <1453485292584-15932.post@n5.nabble.com>
 <1453490558933-15934.post@n5.nabble.com>
In-Reply-To: <1453490558933-15934.post@n5.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

A Tablet is hosted by one and only one TabletServer at any time. The 
only data you are querying is in Tablet(s) hosted by that one TabletServer.

Add more splits to the table which you are heavily querying to spread 
the load across many TabletServers. Load is parallelized in Accumulo by 
creating multiple Tablets (via splits) which can be spread across 
multiple servers.

z11373 wrote:
> Another observation which I really want to know why.
>
> I see 1 tablet server consistently shows high number of waiting scans, i.e.
> '16 (435)' or '14 (476)' on Running Scans column, while the other 19 tablet
> servers all showing '0 (0)' or sometimes showing single digit number. The
> thing I don't understand is what I've seen from the Monitor UI for a table
> at one snapshot for example, and this is more or less consistent from time
> to time (when the test clients are still running).
>
> Server | Query | Running Scans
> ====================
> TServer1 | 24 | 0 (0)
> TServer2 | 37 | 0 (0)
> TServer3 | 40 | 0 (0)
> TServer4 | 1 | 0 (0)
> TServer5 | 0 | 0 (0)
> TServer6 | 57 | 0 (0)
> TServer7 | 5 | 0 (0)
> TServer8 | 4 | 0 (0)
> TServer9 | 7 | 0 (0)
> TServer10 | 0 | 0 (0)
> TServer11 | 56 | 0 (0)
> TServer12 | 124 | 0 (0)
> TServer13 | 25 | 0 (0)
> TServer14 | 121 | 16 (435)
> TServer15 | 36 | 0 (0)
> TServer16 | 21 | 0 (0)
> TServer17 | 3 | 0 (0)
> TServer18 | 107 | 0 (0)
> TServer19 | 21 | 0 (0)
> TServer20 | 92 | 0 (0)
>
> I'd really appreciate if someone could explain what may have happened, or
> can point me to the right direction for starting the investigation. For the
> record, there are 50 test clients, each may create multiple scanners to
> query different data from that table.
>
> Thanks,
> Z
>
>
>
> --
> View this message in context: http://apache-accumulo.1065345.n5.nabble.com/question-on-data-block-cache-tp15906p15934.html
> Sent from the Developers mailing list archive at Nabble.com.