[
https://issues.apache.org/jira/browse/HBASE-22075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798396#comment-16798396
]
Josh Elser commented on HBASE-22075:
------------------------------------
{quote}some files (or parts of files after splitting) can be loaded, some may
fail
{quote}
What is creating multiple files? Doesn't this compact create a single MOB file
and then one reference file to that file?
It looks like we write the MOB file in a tmp dir and then directly mv it into
the mobFamily for the Region whose MOB files we're compacting. Maybe I need to
look farther up the call stack to get it?
{quote}These are artifacts of some code cleaning/modifications. The fileName
argument is not used at all in *bulkloadRefFile* method, but only bulkloadDir,
where ref file is located.
{quote}
Ok, looks like {{bulkloadPathOfPartition}} is an ancestor of
{{bulkloadColumnPath}} which also makes this harder to follow. Thanks for
clarifying that.
> 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)
