hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "NITIN VERMA (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-14048) The REDO operation of AtomicRename of folder doesn't create a placeholder blob for destination folder
Date Thu, 02 Feb 2017 07:32:53 GMT
NITIN VERMA created HADOOP-14048:
------------------------------------

             Summary: The REDO operation of AtomicRename of folder doesn't create a placeholder
blob for destination folder
                 Key: HADOOP-14048
                 URL: https://issues.apache.org/jira/browse/HADOOP-14048
             Project: Hadoop Common
          Issue Type: New Feature
          Components: fs/azure
            Reporter: NITIN VERMA
            Assignee: NITIN VERMA


While doing manual testing, I realized that the crash recovery of AtomicRename operation of
a folder in AzureNativeFileSystem doesn't create a placeholder property blob for destination
folder. Due to this bug, the destination folder can not be renamed again.

Below is how I tested this:
1. Create a test directory as "/test/A"
2. Create 15 block blobs in "/test/A" folder.
3. Run "hadoop fs -mv /test/A /test/B" command and crash it as soon as /test/A-RenamePending.json
file is created.
4. Now run "hadoop fs -lsr /test" command, which should complete the pending rename operation
(redo) as a part of crash recovery. 
5. The REDO method copies the pending files from source folder to destination folder (by consulting
A-RenamePending.json file), but it doesn't create a 0-byte property blob for /test/B folder,
which is a bug as that folder will not be usable for many operations. 




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org


Mime
View raw message