Liu Shaohui created HBASE-15385:
-----------------------------------
Summary: A failed atomic folder rename operation can never
recovery for the destination file deleted in Wasb filesystem
Key: HBASE-15385
URL: https://issues.apache.org/jira/browse/HBASE-15385
Project: HBase
Issue Type: Bug
Components: hadoop-azure
Reporter: Liu Shaohui
Priority: Critical
Fix For: 3.0.0
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.
{quota}
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.
{quote}
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)
