You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Gaurav Kanade (JIRA)" <ji...@apache.org> on 2016/01/06 01:49:39 UTC

[jira] [Updated] (HADOOP-12634) Change Lazy Rename Pending Operation Completion of WASB to address case of potential data loss due to partial copy

     [ https://issues.apache.org/jira/browse/HADOOP-12634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gaurav Kanade updated HADOOP-12634:
-----------------------------------
    Attachment: HADOOP-12634.02.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
>         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)