Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of otis.gospodnetic@gmail.com
 designates 209.85.216.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADSeYa0AOacCKhK9qs9rCeRcsqRdADP-E7TRX0tD9hxj=L--zw@mail.gmail.com>
References: 
 <CADSeYa0AOacCKhK9qs9rCeRcsqRdADP-E7TRX0tD9hxj=L--zw@mail.gmail.com>
Date: Fri, 18 Oct 2013 20:31:54 -0400
Message-ID: 
 <CANNBgP+xZeqghHtBpE48Wq9GUSLUjisbEaV+A37d7zBYXA4OWQ@mail.gmail.com>
Subject: Re: Block cache hit ratio question
From: Otis Gospodnetic <otis.gospodnetic@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=001a1134447486305d04e90d2d7c

--001a1134447486305d04e90d2d7c
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Our SPM for HBase doesn't show per table or region cache stats, and looks
like that is not available yet, but it will let you slice by host and see
changes over time, e.g., as you tune. See http://sematext.com/spm . We use
it for monitoring our own clusters.

Otis
Solr & ElasticSearch Support
http://sematext.com/
On Oct 18, 2013 6:20 PM, "Vaibhav Puranik" <vpuranik@gmail.com> wrote:

> Hi all,
>
> Our HBase is slowing down because of lots of disk reads. We are trying to
> analyze it. We have lots of real time random reads. And We found that HBase
> is constantly reading from disk instead of from memory.
>
> Looks like block cache hit ratio is a good place to start.
>
> Is there any way we can get block cache hit ratio by table or by region? I
> could only find it per region server in region server UI. I couldn't find
> it in API either.
>
> Feel free to suggest any other metrics we should be looking at too.
>
> Thanks,
> Vaibhav
> GumGum
>

--001a1134447486305d04e90d2d7c--