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 "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2014/04/23 01:54:17 UTC
[jira] [Commented] (HDFS-2975) Rename with overwrite flag true can
make NameNode to stuck in safemode on NN (crash + restart).
[ https://issues.apache.org/jira/browse/HDFS-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977636#comment-13977636 ]
Tsz Wo Nicholas Sze commented on HDFS-2975:
-------------------------------------------
Is this still a problem?
> 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: Uma Maheswara Rao G
>
> 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)