Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 401991066A for ; Fri, 30 May 2014 14:31:04 +0000 (UTC) Received: (qmail 93066 invoked by uid 500); 30 May 2014 14:31:04 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 93039 invoked by uid 500); 30 May 2014 14:31:04 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 93030 invoked by uid 99); 30 May 2014 14:31:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 May 2014 14:31:04 +0000 Date: Fri, 30 May 2014 14:31:04 +0000 (UTC) From: "Brandon Williams (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7324) Strange warnings during pig-test 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/CASSANDRA-7324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013684#comment-14013684 ] Brandon Williams commented on CASSANDRA-7324: --------------------------------------------- Thinking about it a bit more, I think the problem is that without this commit it errors so quickly that the warnings are never produced. > Strange warnings during pig-test > -------------------------------- > > Key: CASSANDRA-7324 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7324 > Project: Cassandra > Issue Type: Bug > Components: Tests > Reporter: Brandon Williams > Assignee: Brandon Williams > Priority: Minor > Fix For: 2.1.0 > > > Not present in 2.0, we have strange but seemingly harmless warnings when running pig-test on 2.1: > {noformat} > [junit] 14/05/29 22:21:53 WARN util.MBeans: Hadoop:service=DataNode,name=FSDatasetState-UndefinedStorageId-1779863485 > [junit] javax.management.InstanceNotFoundException: Hadoop:service=DataNode,name=FSDatasetState-UndefinedStorageId-1779863485 > [junit] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095) > [junit] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427) > [junit] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415) > [junit] at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546) > [junit] at org.apache.hadoop.metrics2.util.MBeans.unregister(MBeans.java:71) > [junit] at org.apache.hadoop.hdfs.server.datanode.FSDataset.shutdown(FSDataset.java:2067) > [junit] at org.apache.hadoop.hdfs.server.datanode.DataNode.shutdown(DataNode.java:799) > [junit] at org.apache.hadoop.hdfs.MiniDFSCluster.shutdownDataNodes(MiniDFSCluster.java:566) > [junit] at org.apache.hadoop.hdfs.MiniDFSCluster.shutdown(MiniDFSCluster.java:550) > [junit] at org.apache.pig.test.MiniGenericCluster.shutdownMiniDfsClusters(MiniGenericCluster.java:87) > [junit] at org.apache.pig.test.MiniGenericCluster.shutdownMiniDfsAndMrClusters(MiniGenericCluster.java:77) > [junit] at org.apache.pig.test.MiniGenericCluster.shutDown(MiniGenericCluster.java:68) > [junit] at org.apache.cassandra.pig.PigTestBase.oneTimeTearDown(PigTestBase.java:77) > [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [junit] at java.lang.reflect.Method.invoke(Method.java:606) > [junit] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > [junit] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > [junit] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > [junit] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:37) > [junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:220) > [junit] at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39) > [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518) > [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052) > [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906) > [junit] 14/05/29 22:21:53 WARN datanode.FSDatasetAsyncDiskService: AsyncDiskService has already shut down. > {noformat} -- This message was sent by Atlassian JIRA (v6.2#6252)