[jira] [Resolved] (HDFS-4208) NameNode could be stuck in SafeMode due to never-created blocks

["Suresh Srinivas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Srinivas resolved HDFS-4208.
-----------------------------------

          Resolution: Fixed
       Fix Version/s: 1.1.1
    Target Version/s: 1.1.1
        Hadoop Flags: Reviewed

I committed the patch to branch-1 and branch-1.1.

Thank you Brandon!
                
> NameNode could be stuck in SafeMode due to never-created blocks
> ---------------------------------------------------------------
>
>                 Key: HDFS-4208
>                 URL: https://issues.apache.org/jira/browse/HDFS-4208
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 1.1.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>            Priority: Critical
>             Fix For: 1.1.1
>
>         Attachments: HDFS-4208.branch-1.patch, HDFS-4208.branch-1.patch, HDFS-4208.branch-1.patch
>
>
> In one test case, NameNode allocated a block and then was killed before the client got the addBlock response. After NameNode restarted, it couldn't get out of SafeMode waiting for the block which was never created. In trunk, NameNode can get out of SafeMode since it only counts complete blocks. However branch-1 doesn't have the clear notion of under-constructioned-block in Namenode. 
> JIRA HDFS-4212 is to track the never-created-block issue and this JIRA is to fix NameNode in branch-1 so it can get out of SafeMode when never-created-block exists.
> The proposed idea is for SafeMode not to count the zero-sized last block in an under-construction file as part of total blcok count.

--
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