hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gaurav Kanade (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12634) Change Lazy Rename Pending Operation Completion of WASB to address case of potential data loss due to partial copy
Date Thu, 10 Dec 2015 22:19:11 GMT

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

Gaurav Kanade updated HADOOP-12634:
-----------------------------------
    Description: 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

> 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
>            Priority: Critical
>
> 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)

Mime
View raw message