Liu Shaohui created HDFS-9897:
---------------------------------

             Summary: A failed atomic folder rename operation can never 
recovery for the destination file is deleted in Wasb filesystem
                 Key: HDFS-9897
                 URL: https://issues.apache.org/jira/browse/HDFS-9897
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Liu Shaohui
            Priority: Critical




When using Wsab file system, we found that a failed atomic folder rename 
operation can never recovery for the destination file deleted in Wasb 
filesystem.
{code}
ls: Attempting to complete rename of file 
hbase/azurtst-xiaomi/data/default/YCSBTest/.tabledesc during folder rename 
redo, and file was not found in source or destination.
{code}

The reason is the the file is renamed to the destination file before the crash, 
and the destination file is deleted by another process after crash. So the 
recovery is blocked during finishing the rename operation of this file when 
found the source and destination files all don't exist.

See: NativeAzureFileSystem.java #finishSingleFileRename

Another serious problem is that the recovery of atomic rename operation may 
delete new created file which is same name as the source file, because the file 
system don't check if there are rename operation need be redo.

Suggestions are welcomed~




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

Reply via email to