Return-Path: Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: (qmail 9847 invoked from network); 26 Oct 2010 23:26:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Oct 2010 23:26:40 -0000 Received: (qmail 87365 invoked by uid 500); 26 Oct 2010 23:26:40 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 87336 invoked by uid 500); 26 Oct 2010 23:26:40 -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 87327 invoked by uid 99); 26 Oct 2010 23:26:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Oct 2010 23:26:40 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Oct 2010 23:26:39 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9QNQJpK027804 for ; Tue, 26 Oct 2010 23:26:19 GMT Message-ID: <16912320.90761288135579257.JavaMail.jira@thor> Date: Tue, 26 Oct 2010 19:26:19 -0400 (EDT) From: "Gary Helmling (JIRA)" To: issues@hbase.apache.org Subject: [jira] Commented: (HBASE-3102) Enhance HBase rMetrics for Long-running Stats In-Reply-To: <19279840.70801286774072673.JavaMail.jira@thor> 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-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925194#action_12925194 ] Gary Helmling commented on HBASE-3102: -------------------------------------- @Nicolas: I agree that the naming issue isn't critical. It's a bit wonky but not a big deal. And understood that this is pushed down on us from the Hadoop metrics limitation. I'm fine with closing this out and opening a new JIRA (low priority) to address the naming issue as time allows. Hadoop metrics are already slated for an overhaul, hopefully in time for 0.22: https://issues.apache.org/jira/browse/HADOOP-6728 I hope that those changes will make some of these issues a bit easier. Will dig into the discussion there when I can. Encourage you to do the same if you see anything. > Enhance HBase rMetrics for Long-running Stats > --------------------------------------------- > > Key: HBASE-3102 > URL: https://issues.apache.org/jira/browse/HBASE-3102 > Project: HBase > Issue Type: Improvement > Components: regionserver > Reporter: Nicolas Spiegelberg > Assignee: Nicolas Spiegelberg > Fix For: 0.90.0 > > Attachments: HBASE-3102_90.patch > > > Example: a useful metric to observe track is compaction count + duration. Since compactions are long running and only happen infrequently, the avg/opcount stats are should be reset longer than the default polling period (5 sec). In addition to 'hbase.period', we should allow a different duration after which long-running metrics should expire. This would also fix our existing metrics problem where min/max stats are never reset until the process is restarted/upgraded. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.