[ https://issues.apache.org/jira/browse/HDFS-14030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673612#comment-16673612 ]
Wei-Chiu Chuang commented on HDFS-14030: ---------------------------------------- Actually, this error is generated by querying /jmx, and the queries are sent by monitoring systems like Cloudera Manager sends these requests regardless the state of DataNode. > Add query whether storage has been initialized to DN's JMXBean > -------------------------------------------------------------- > > Key: HDFS-14030 > URL: https://issues.apache.org/jira/browse/HDFS-14030 > Project: Hadoop HDFS > Issue Type: Improvement > Components: hdfs > Reporter: Adam Antal > Assignee: Adam Antal > Priority: Minor > Attachments: HDFS-14030.001.patch > > > During the short period while the DN is starting and the storage is not yet > available we get the following errors: > {noformat} > ERROR org.apache.hadoop.jmx.JMXJsonServlet: getting attribute VolumeInfo of > Hadoop:service=DataNode,name=DataNodeInfo threw an exception > javax.management.RuntimeMBeanException: java.lang.NullPointerException: > Storage not yet initialized > {noformat} > I suggest to add an option to the DataNodeMXBean to query whether the storage > has been initialized or not to surpass the exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org