[
https://issues.apache.org/jira/browse/HDFS-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12907842#action_12907842
]
Tanping Wang commented on HDFS-1386:
------------------------------------
In HDFS1318, we introduced two MXBean for data node and name node respectively
in Datanode.java and FSNamesystem.java. Due to the improper un-registration of
the two MXBeans, there are exceptions throwing from time to time, below is an
example,
2010-08-02 15:38:06,584 WARN namenode.FSNamesystem
(FSNamesystem.java:registerMXBean(5143)) - Failed to register
NameNodeMXBean
javax.management.InstanceAlreadyExistsException: HadoopInfo:type=NameNodeInfo
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
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.hdfs.server.namenode.FSNamesystem.registerMXBean(FSNamesystem.java:5141)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:382)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:315)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:254)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:434)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1166)
at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:270)
at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:121)
at
org.apache.hadoop.hdfs.TestFileAppend.testSimpleFlush(TestFileAppend.java:222)
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 junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:79)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768)
This fix introduce unregister() method which unregister the info MXBean in
Datanode and namenode.
> unregister namenode datanode info MXBean
> ----------------------------------------
>
> Key: HDFS-1386
> URL: https://issues.apache.org/jira/browse/HDFS-1386
> Project: Hadoop HDFS
> Issue Type: New Feature
> Affects Versions: 0.22.0
> Reporter: Tanping Wang
> Assignee: Tanping Wang
> Fix For: 0.22.0
>
>
> Currently Namenode and Datanode web page needs to be scraped by scripts to
> get this information. Having an interface where this structured information
> is provided, will help building scripts around it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
