You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2013/07/29 05:15:48 UTC
[jira] [Updated] (AMBARI-2513) Update hdfs-site config to new
'stale' configuration used in hadoop 1.2+
[ https://issues.apache.org/jira/browse/AMBARI-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated AMBARI-2513:
----------------------------------
Attachment: AMBARI-2513.patch
Attached patch - synced up the local repo metdata with the non local repo ones.
> Update hdfs-site config to new 'stale' configuration used in hadoop 1.2+
> ------------------------------------------------------------------------
>
> Key: AMBARI-2513
> URL: https://issues.apache.org/jira/browse/AMBARI-2513
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.2.3
> Reporter: Nate Cole
> Assignee: Nate Cole
> Fix For: 1.2.5
>
> Attachments: AMBARI-2513.patch, AMBARI-2513.patch
>
>
> In Hadoop 1.2 which is shipped with HDP 1.3, the configuration in hdfs-site.xml for detecting stale nodes has changed. Ambari still exposed the configuration for Hadoop 1.1.
> The old configuration needs to be removed:
> <!-- stale mode - branch 1.1.1+ -->
> <property>
> <name>dfs.namenode.check.stale.datanode</name>
> <value>true</value>
> </property>
> And replaced with the new configuration switches:
> <!-- stale mode - 1.2+ -->
> <property>
> <name>dfs.namenode.avoid.read.stale.datanode</name>
> <value>true</value>
> </property>
> <property>
> <name>dfs.namenode.avoid.write.stale.datanode</name>
> <value>true</value>
> </property>
> <property>
> <name>dfs.namenode.write.stale.datanode.ratio</name>
> <value>1.0f</value>
> </property>
> <property>
> <name>dfs.namenode.stale.datanode.interval</name>
> <value>30000</value>
> <description>Datanode is stale after not getting a heartbeat in this interval in ms</description>
> </property>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira