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 58EB51100A for ; Thu, 12 Jun 2014 17:15:03 +0000 (UTC) Received: (qmail 75929 invoked by uid 500); 12 Jun 2014 17:15:03 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 75877 invoked by uid 500); 12 Jun 2014 17:15:03 -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 75866 invoked by uid 99); 12 Jun 2014 17:15:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2014 17:15:03 +0000 Date: Thu, 12 Jun 2014 17:15:03 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-4089) blockCache contents report MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029429#comment-14029429 ] stack commented on HBASE-4089: ------------------------------ How you get the NPE [~mantonov]? It happens when you run the suite? If I run the single test it seems to pass fine and passed above for the hadoopqa run. That said, there is something here for sure if you are seeing a regular failure. > 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: stack > Fix For: 0.99.0 > > Attachments: 4089.wip.txt, 4089.wip.v2.txt, 4089v3.txt, 4089v4.txt, 4089v6.txt, 4089v7.txt, 4089v7.txt, 4089v8.txt, bc_basic.png, bc_bucketcache.png, bc_buckets.png, bc_config.png, bc_l1.png, bc_l2_buckets.png, bc_showing_buckets_start.png, bc_slabs.png, bc_slabs.png, bc_stats.png, hbase_4089_blockcachereport.pdf, java_blockcache_checkpoint_2011_08_11.patch > > > 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 was sent by Atlassian JIRA (v6.2#6252)