[
https://issues.apache.org/jira/browse/HADOOP-14048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Liu updated HADOOP-14048:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.0.0-alpha3
2.8.0
Status: Resolved (was: Patch Available)
+1
I have committed to {{trunk}}, {{branch-2}} and {{branch-2.8}} branches. When
committing, I removed the changes of importing code, which are unnecessary and
might bring back-port conflicts. Thanks for your contribution,
[[email protected]]; thanks for your review [~gouravk].
> REDO operation of WASB#AtomicRename of folder should create 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
> Fix For: 2.8.0, 3.0.0-alpha3
>
> Attachments: HADOOP-14048.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
