hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HDFS-2975) Rename with overwrite flag true can make NameNode to stuck in safemode on NN (crash + restart).
Date Fri, 22 Aug 2014 03:04:11 GMT

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

Uma Maheswara Rao G reassigned HDFS-2975:
-----------------------------------------

    Assignee: Yi Liu  (was: Uma Maheswara Rao G)

Yes, Nicholas. I looked at the code. This should be fixed.

> Rename with overwrite flag true can make NameNode to stuck in safemode on NN (crash +
restart).
> -----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-2975
>                 URL: https://issues.apache.org/jira/browse/HDFS-2975
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 0.24.0
>            Reporter: Uma Maheswara Rao G
>            Assignee: Yi Liu
>
> When we rename the file with overwrite flag as true, it will delete the destination file
blocks. After deleting the blocks, whenever it releases the fsNameSystem lock, NN can give
the invalidation work to corresponding DNs to delete the blocks.
> Parallaly it will sync the rename related edits to editlog file. At this step before
NN sync the edits if NN crashes, NN can stuck into safemode on restart. This is because block
already deleted from the DN as part of invalidations. But dst file still exist as rename edits
not persisted in log file and no DN will report that blocks now.
> This is similar to HDFS-2815
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message