[
https://issues.apache.org/jira/browse/HADOOP-12634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-12634:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
+1 for patch v02. The JavaDoc warnings from the last pre-commit run are
pre-existing warnings unrelated to this patch. The patch shifted line numbers,
which made them look like new warnings.
I have committed this to trunk, branch-2 and branch-2.8. [~gouravk], thank you
for the patch.
> 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)
