[ 
https://issues.apache.org/jira/browse/OOZIE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204345#comment-13204345
 ] 

[email protected] commented on OOZIE-601:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3820/#review4961
-----------------------------------------------------------


Testcases getting stuck. Seems like its due to changing the version from 
0.20.104.2 to 1.0.0. 

Seeing the following trace repeatedly in testcases for oozie-core:


Starting DataNode 0 with dfs.data.dir: 
build/test/data/dfs/data/data1,build/test/data/dfs/data/data2
12/02/08 23:30:49 WARN impl.MetricsSystemImpl: Metrics system not started: 
Cannot locate configuration: tried hadoop-metrics2-datanode.properties, 
hadoop-metrics2.properties
12/02/08 23:30:49 WARN util.MBeans: 
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:1491)
        at 
org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:1467)
        at 
org.apache.hadoop.hdfs.MiniDFSCluster.startDataNodes(MiniDFSCluster.java:417)
        at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:280)
        at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:124)
        at 
org.apache.oozie.test.XTestCase.setUpEmbeddedHadoop(XTestCase.java:665)
        at org.apache.oozie.test.XTestCase.setUp(XTestCase.java:247)
        at org.apache.oozie.test.XFsTestCase.setUp(XFsTestCase.java:58)
        at junit.framework.TestCase.runBare(TestCase.java:125)
        at junit.framework.TestResult$1.protect(TestResult.java:106)
        at junit.framework.TestResult.runProtected(TestResult.java:124)
        at junit.framework.TestResult.run(TestResult.java:109)
        at junit.framework.TestCase.run(TestCase.java:118)
        at junit.framework.TestSuite.runTest(TestSuite.java:208)
        at junit.framework.TestSuite.run(TestSuite.java:203)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
        at 
org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:109)
        at 
org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:81)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:101)
        at $Proxy0.invoke(Unknown Source)
        at 
org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:139)
        at 
org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:82)
        at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:81)


- Virag


On 2012-02-09 05:13:30, Alejandro Abdelnur wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/3820/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2012-02-09 05:13:30)
bq.  
bq.  
bq.  Review request for oozie and Mohammad Islam.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  backporting OOZIE-601 to branch-3.1
bq.  
bq.  
bq.  This addresses bug OOZIE-601.
bq.      https://issues.apache.org/jira/browse/OOZIE-601
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    branches/branch-3.1/client/pom.xml 1242217 
bq.    branches/branch-3.1/core/pom.xml 1242217 
bq.    branches/branch-3.1/distro/pom.xml 1242217 
bq.    branches/branch-3.1/docs/pom.xml 1242217 
bq.    branches/branch-3.1/examples/pom.xml 1242217 
bq.    branches/branch-3.1/minitest/pom.xml 1242217 
bq.    branches/branch-3.1/pom.xml 1242217 
bq.    branches/branch-3.1/sharelib/pom.xml 1242217 
bq.    branches/branch-3.1/webapp/pom.xml 1242217 
bq.  
bq.  Diff: https://reviews.apache.org/r/3820/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  did a full build
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Alejandro
bq.  
bq.


                
> Oozie's POMs should use org.apache.oozie as group
> -------------------------------------------------
>
>                 Key: OOZIE-601
>                 URL: https://issues.apache.org/jira/browse/OOZIE-601
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> Currently they are using com.yahoo.oozie

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to