[
https://issues.apache.org/jira/browse/HDFS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767004#action_12767004
]
Hadoop QA commented on HDFS-645:
--------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12420340/HDFS-645-0.20.1.patch
against trunk revision 826149.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/33/console
This message is automatically generated.
> 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: name-node
> Affects Versions: 0.20.1
> Reporter: Qi Liu
> Assignee: Qi Liu
> Attachments: HDFS-645-0.18.3.patch, HDFS-645-0.20.1.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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
