[
https://issues.apache.org/jira/browse/HBASE-22075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798374#comment-16798374
]
Vladimir Rodionov commented on HBASE-22075:
-------------------------------------------
{quote}
Another question: In the case where we successfully created the new MOB file
but the bulk loading of the ref file failed, how is deleting the new mob file
causing data loss? The bulk load should be atomic, right? (Either all files are
loaded or no files are loaded) I would think that if the bulk load of the ref
file failed, we would be safe to get rid of that new MOB file because we still
have all of the old MOB files.
{quote}
Bulkload is atomic per region only. If you have file(s) which span(s) several
regions - no atomicity for you. In the latter case, some files (or parts of
files after splitting) can be loaded, some may fail. You get partially
successful operation and, as a result, - data loss (MOB was deleted bc of a
compaction failure), but some parts of a new reference file(s) were loaded.
> Potential data loss when MOB compaction fails
> ---------------------------------------------
>
> Key: HBASE-22075
> URL: https://issues.apache.org/jira/browse/HBASE-22075
> Project: HBase
> Issue Type: Bug
> Components: mob
> Affects Versions: 2.1.0, 2.0.0, 2.0.1, 2.1.1, 2.0.2, 2.0.3, 2.1.2, 2.0.4,
> 2.1.3
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Critical
> Labels: mob
> Fix For: 2.2.0, 2.0.5, 2.1.4
>
> Attachments: HBASE-22075-v1.patch
>
>
> When MOB compaction fails during last step (bulk load of a newly created
> reference file) there is a high chance of a data loss due to partially loaded
> reference file, cells of which refer to (now) non-existent MOB file. The
> newly created MOB file is deleted automatically in case of a MOB compaction
> failure, but some cells with the references to this file might be loaded to
> HBase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
