Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 6 Aug 2011 22:37:27 +0000 (UTC)
From: "Doug Meil (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1599622073.14203.1312670247247.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1824712261.7522.1310503739884.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HBASE-4089) blockCache contents report
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Meil reassigned HBASE-4089:
--------------------------------

    Assignee: Doug Meil

> blockCache contents report
> --------------------------
>
>                 Key: HBASE-4089
>                 URL: https://issues.apache.org/jira/browse/HBASE-4089
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Doug Meil
>            Assignee: Doug Meil
>         Attachments: hbase_4089_blockcachereport.pdf
>
>
> Summarized block-cache report for a RegionServer would be helpful.  For example ...
> table1
>   cf1   100 blocks, totalBytes=yyyyy, averageTimeInCache=XXXX hours
>   cf2   200 blocks, totalBytes=zzzzz, averageTimeInCache=XXXX hours
> table2
>   cf1  75 blocks, totalBytes=yyyyy, averageTimeInCache=XXXX hours
>   cf2 150 blocks, totalBytes=zzzzz, averageTimeInCache=XXXX hours
> ... Etc.
> The current metrics list blockCacheSize and blockCacheFree, but there is no way to know what's in there.  Any single block isn't really important, but the patterns of what CF/Table they came from, how big are they, and how long (on average) they've been in the cache, are important.
> No such interface exists in HRegionInterface.  But I think it would be helpful from an operational perspective.
> Updated (7-29):  Removing suggestion for UI.  I would be happy just to get this report on a configured interval dumped to a log file.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira