You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Dean (JIRA)" <ji...@apache.org> on 2015/06/09 12:09:00 UTC

[jira] [Commented] (HDFS-8384) Allow NN to startup if there are files having a lease but are not under construction

    [ https://issues.apache.org/jira/browse/HDFS-8384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578663#comment-14578663 ] 

Dean commented on HDFS-8384:
----------------------------

Is there a workaround ?

> Allow NN to startup if there are files having a lease but are not under construction
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-8384
>                 URL: https://issues.apache.org/jira/browse/HDFS-8384
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Minor
>
> When there are files having a lease but are not under construction, NN will fail to start up with
> {code}
> 15/05/12 00:36:31 ERROR namenode.FSImage: Unable to save image for /hadoop/hdfs/namenode
> java.lang.IllegalStateException
>         at com.google.common.base.Preconditions.checkState(Preconditions.java:129)
>         at org.apache.hadoop.hdfs.server.namenode.LeaseManager.getINodesUnderConstruction(LeaseManager.java:412)
>         at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFilesUnderConstruction(FSNamesystem.java:7124)
>         ...
> {code}
> The actually problem is that the image could be corrupted by bugs like HDFS-7587.  We should have an option/conf to allow NN to start up so that the problematic files could possibly be deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)