hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Biju Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6688) Hadoop JMX stats are not refreshed
Date Tue, 15 Jul 2014 21:55:08 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062721#comment-14062721

Biju Nair commented on HDFS-6688:

Thanks Andrew. By waiting for more than 10 mins, the entries were updated correctly. Reading
through http://hadoop.apache.org/docs/r2.4.0/hadoop-project-dist/hadoop-hdfs/hdfs-default.xml
the default datanode heartbeat seems to be dfs.heartbeat.interval - 3 secs. Is this a change
coming up in 2.4? Is there a reason for the default 10.5 min wait time? 

> Hadoop JMX stats are not refreshed
> ----------------------------------
>                 Key: HDFS-6688
>                 URL: https://issues.apache.org/jira/browse/HDFS-6688
>             Project: Hadoop HDFS
>          Issue Type: Bug
>         Environment: Ubuntu
>            Reporter: Biju Nair
> Even when the HDFS datanode process is stopped the JMX attribute Hadoop.NameNode.FSNamesystemState.NumLiveDataNodes/NumDeadDataNodes
attribute values doesn't change. Also Hadoop.NameNode.NameNodeInfo.Attributes.LiveNodes shows
the stopped datanode details. If these attributes reflect the actual changes in the datanode,
they can be used to monitor the health of the HDFS cluster which currently can't be used.

This message was sent by Atlassian JIRA

View raw message