Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E4C9F6DA2 for ; Fri, 29 Jul 2011 10:56:44 +0000 (UTC) Received: (qmail 85735 invoked by uid 500); 29 Jul 2011 10:56:44 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 85581 invoked by uid 500); 29 Jul 2011 10:56:37 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 85567 invoked by uid 99); 29 Jul 2011 10:56:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jul 2011 10:56:35 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jul 2011 10:56:32 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 67F1C91C79 for ; Fri, 29 Jul 2011 10:56:10 +0000 (UTC) Date: Fri, 29 Jul 2011 10:56:10 +0000 (UTC) From: "Doug Meil (JIRA)" To: issues@hbase.apache.org Message-ID: <1710180417.18260.1311936970422.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1824712261.7522.1310503739884.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (HBASE-4089) blockCache contents report MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Meil updated HBASE-4089: ----------------------------- Description: A UI that would display a 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, so this is not just a UI request also an API change. But I think it would be helpful from an operational perspective. was: A UI that would display a 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, so this is not just a UI request also an API change. But I think it would be helpful from an operational perspective. Summary: blockCache contents report (was: UI for blockCache contents report) > blockCache contents report > -------------------------- > > Key: HBASE-4089 > URL: https://issues.apache.org/jira/browse/HBASE-4089 > Project: HBase > Issue Type: New Feature > Reporter: Doug Meil > > A UI that would display a 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, so this is not just a UI request also an API change. But I think it would be helpful from an operational perspective. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira