[
https://issues.apache.org/jira/browse/HDFS-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125759#comment-13125759
]
Hudson commented on HDFS-2422:
------------------------------
Integrated in Hadoop-Hdfs-trunk #828 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/828/])
Move line for HDFS-2422 under 0.23 instead of 0.24.
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1182220
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> The NN should tolerate the same number of low-resource volumes as failed
> volumes
> --------------------------------------------------------------------------------
>
> Key: HDFS-2422
> URL: https://issues.apache.org/jira/browse/HDFS-2422
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Jeff Bean
> Assignee: Aaron T. Myers
> Fix For: 0.23.0
>
> Attachments: HDFS-2422.patch
>
>
> We encountered a situation where the namenode dropped into safe mode after a
> temporary outage of an NFS mount.
> At 12:10 the NFS server goes offline
> Oct 8 12:10:05 <namenode> kernel: nfs: server <nfs host> not responding,
> timed out
> This caused the namenode to conclude resource issues:
> 2011-10-08 12:10:34,848 WARN
> org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker: Space
> available on volume '<nfs host>' is 0, which is below the configured reserved
> amount 104857600
> Temporary loss of NFS mount shouldn't cause safemode.
--
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
