[
https://issues.apache.org/jira/browse/HADOOP-12634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086220#comment-15086220
]
Hudson commented on HADOOP-12634:
---------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9059 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9059/])
HADOOP-12634. Change Lazy Rename Pending Operation Completion of WASB to
(cnauroth: rev 978bbdfeb2d12efd6e750da6a14849e072fb814b)
* hadoop-common-project/hadoop-common/CHANGES.txt
*
hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/NativeAzureFileSystem.java
*
hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azure/TestNativeAzureFileSystemLive.java
> Change Lazy Rename Pending Operation Completion of WASB to address case of
> potential data loss due to partial copy
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-12634
> URL: https://issues.apache.org/jira/browse/HADOOP-12634
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Gaurav Kanade
> Assignee: Gaurav Kanade
> Priority: Critical
> Fix For: 2.8.0
>
> Attachments: HADOOP-12634.01.patch, HADOOP-12634.02.patch
>
>
> HADOOP-12334 changed mode of Copy Operation of HBase WAL Archiving to bypass
> Azure Storage Throttling after retries. This was via client side copy.
> However a process crash when the copy is partially done would result in a
> scenario where the source and destination blobs will have different contents
> and lazy rename pending operation will not handle this thus causing data
> loss. We need to fix the lazy rename pending operation to address this issue
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
