[
https://issues.apache.org/jira/browse/HDFS-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HDFS-2975:
--------------------------------------
Resolution: Fixed
Fix Version/s: 2.6.0
3.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
I have just committed this to trunk and branch-2. Thanks a lot for the patch Yi.
Also thanks a lot, Vinay for the review!
> 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
> Reporter: Uma Maheswara Rao G
> Assignee: Yi Liu
> Fix For: 3.0.0, 2.6.0
>
> Attachments: HDFS-2975.001.patch, HDFS-2975.002.patch
>
>
> 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.3.4#6332)
