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 63354DF61 for ; Fri, 7 Dec 2012 14:09:23 +0000 (UTC) Received: (qmail 75667 invoked by uid 500); 7 Dec 2012 14:09:23 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 75603 invoked by uid 500); 7 Dec 2012 14:09:22 -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 75583 invoked by uid 99); 7 Dec 2012 14:09:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2012 14:09:22 +0000 Date: Fri, 7 Dec 2012 14:09:22 +0000 (UTC) From: "nkeywal (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-4709) Hadoop metrics2 setup in test MiniDFSClusters spewing JMX errors 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-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-4709: --------------------------- Attachment: 4709.v2.patch > Hadoop metrics2 setup in test MiniDFSClusters spewing JMX errors > ---------------------------------------------------------------- > > Key: HBASE-4709 > URL: https://issues.apache.org/jira/browse/HBASE-4709 > Project: HBase > Issue Type: Bug > Components: test > Affects Versions: 0.92.0, 0.94.0, 0.94.1 > Reporter: Gary Helmling > Priority: Minor > Fix For: 0.96.0 > > Attachments: 4709.v2.patch, 4709.v2.patch, 4709_workaround.v1.patch > > > Since switching over HBase to build with Hadoop 0.20.205.0, we've been getting a lot of metrics related errors in the log files for tests: > {noformat} > 2011-10-30 22:00:22,858 INFO [main] log.Slf4jLog(67): jetty-6.1.26 > 2011-10-30 22:00:22,871 INFO [main] log.Slf4jLog(67): Extract jar:file:/home/jenkins/.m2/repository/org/apache/hadoop/hadoop-core/0.20.205.0/hadoop-core-0.20.205.0.jar!/webapps/datanode to /tmp/Jetty_localhost_55751_datanode____.kw16hy/webapp > 2011-10-30 22:00:23,048 INFO [main] log.Slf4jLog(67): Started SelectChannelConnector@localhost:55751 > Starting DataNode 1 with dfs.data.dir: /home/jenkins/jenkins-slave/workspace/HBase-TRUNK/trunk/target/test-data/7ba65a16-03ad-4624-b769-57405945ef58/dfscluster_3775fc23-1b51-4966-8133-205564bae762/dfs/data/data3,/home/jenkins/jenkins-slave/workspace/HBase-TRUNK/trunk/target/test-data/7ba65a16-03ad-4624-b769-57405945ef58/dfscluster_3775fc23-1b51-4966-8133-205564bae762/dfs/data/data4 > 2011-10-30 22:00:23,237 WARN [main] impl.MetricsSystemImpl(137): Metrics system not started: Cannot locate configuration: tried hadoop-metrics2-datanode.properties, hadoop-metrics2.properties > 2011-10-30 22:00:23,237 WARN [main] util.MBeans(59): Hadoop:service=DataNode,name=MetricsSystem,sub=Control > javax.management.InstanceAlreadyExistsException: MXBean already registered with name Hadoop:service=NameNode,name=MetricsSystem,sub=Control > at com.sun.jmx.mbeanserver.MXBeanLookup.addReference(MXBeanLookup.java:120) > at com.sun.jmx.mbeanserver.MXBeanSupport.register(MXBeanSupport.java:143) > at com.sun.jmx.mbeanserver.MBeanSupport.preRegister2(MBeanSupport.java:183) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:941) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) > at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) > at org.apache.hadoop.metrics2.util.MBeans.register(MBeans.java:56) > at org.apache.hadoop.metrics2.impl.MetricsSystemImpl.initSystemMBean(MetricsSystemImpl.java:500) > at org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:140) > at org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:40) > at org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50) > at org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:1483) > at org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:1459) > at org.apache.hadoop.hdfs.MiniDFSCluster.startDataNodes(MiniDFSCluster.java:417) > at org.apache.hadoop.hdfs.MiniDFSCluster.(MiniDFSCluster.java:280) > at org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:349) > at org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:518) > at org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:474) > at org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:461) > {noformat} > This seems to be due to errors initializing the new hadoop metrics2 code by default, when running in a mini cluster. The errors themselves seem to be harmless -- they're not breaking any tests -- but we should figure out what configuration we need to eliminate them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira