You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/24 02:32:39 UTC
[jira] [Resolved] (HDFS-645) Namenode does not leave safe mode even
if all blocks are available
[ https://issues.apache.org/jira/browse/HDFS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved HDFS-645.
-----------------------------------
Resolution: Fixed
This was fixed in 1.x at some point.
> Namenode does not leave safe mode even if all blocks are available
> ------------------------------------------------------------------
>
> Key: HDFS-645
> URL: https://issues.apache.org/jira/browse/HDFS-645
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.20.1, 0.21.0, 0.22.0
> Reporter: Qi Liu
> Assignee: Qi Liu
> Attachments: HDFS-645-0.18.3.patch, HDFS-645-0.20.1.patch, HDFS-645.patch, HDFS-645.patch
>
>
> When the safe mode threshold is set to 1.0f, sometimes the name node does not leave safe mode even if all blocks are available. This is caused by floating point number division and comparison issues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)