Return-Path: Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: (qmail 12896 invoked from network); 3 Jan 2011 23:28:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jan 2011 23:28:07 -0000 Received: (qmail 44270 invoked by uid 500); 3 Jan 2011 23:28:07 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 44175 invoked by uid 500); 3 Jan 2011 23:28:07 -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 44167 invoked by uid 99); 3 Jan 2011 23:28:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jan 2011 23:28:07 +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; Mon, 03 Jan 2011 23:28:07 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p03NRkNq022001 for ; Mon, 3 Jan 2011 23:27:46 GMT Message-ID: <13543269.120611294097266246.JavaMail.jira@thor> Date: Mon, 3 Jan 2011 18:27:46 -0500 (EST) From: "stack (JIRA)" To: issues@hbase.apache.org Subject: [jira] Commented: (HBASE-3405) Allow HBaseRpcMetrics to register custom interface methods In-Reply-To: <1498054.78881293772725746.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-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977013#action_12977013 ] stack commented on HBASE-3405: ------------------------------ Would this be hard to do Gary? Seems straight-forward and something we might pull into 0.90 for James? > Allow HBaseRpcMetrics to register custom interface methods > ---------------------------------------------------------- > > Key: HBASE-3405 > URL: https://issues.apache.org/jira/browse/HBASE-3405 > Project: HBase > Issue Type: Improvement > Components: ipc > Reporter: Gary Helmling > Priority: Minor > > Opened from comments on HBASE-2997. James Kennedy notes: > {quote} > HBaseRpcMetrics is now logging a WARN message every time it encounters an unregistered RPC method. > In my case I now get huge log files filled with these warnings because the hbase-trx transactional extension of HBase uses a subclass of HRegionServer that adds new interface methods. > It's easy enough to tell log4j to ignore HBaseRpcMetrics output. > However, it would be nice if the Server/HRegionServer HBaseRpcMetrics mechanism was more extensible so I could pass down new interfaces or grab the HBaseRpcMetrics object to add interfaces from up top... > {quote} > {{HBaseRpcMetrics}} already has a public method {{createMetrics(Class)}} to register method counters. We just need a way to expose the metrics class to allow the region server subclass to call it -- add a {{getMetrics()}} method to {{RpcServer}} and {{HBaseServer}}. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.