[
https://issues.apache.org/jira/browse/HBASE-17852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216220#comment-16216220
]
Josh Elser commented on HBASE-17852:
------------------------------------
bq. On looking at the patch, it looks like we have a backup system table and
then a whole new table for bulk loaded materials. A whole system table just for
bulk loaded files?
Yeah, as I recall, Vlad ran into a case where, when trying to make sure that we
didn't lose files in incremental backups, we grabbed a table-level lock.
Because this lock was on the {{hbase:backup}} table, it introduced a situation
where the system deadlocked. By introducing a table which is explicitly
tracking the bulk-loaded files, it avoids this deadlock scenario.
bq. Whats going on in here? Is it written up anywhere? Are we implementing our
own transaction management as the below comment would suggest?
My understanding is that, functionality-wise, we're not actually changing
anything. This is really just automatically deploying the BackupObserver
instead of forcing it to be deployed automatically.
I'm not sure if [~tedyu] has more depth to provide some more context. I do know
that Vlad is traveling for familial reasons this week and is likely slow to
respond.
[~stack], would you prefer I hold off and re-tag this for beta-1?
> Add Fault tolerance to HBASE-14417 (Support bulk loaded files in incremental
> backup)
> ------------------------------------------------------------------------------------
>
> Key: HBASE-17852
> URL: https://issues.apache.org/jira/browse/HBASE-17852
> Project: HBase
> Issue Type: Sub-task
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-17852-v1.patch, HBASE-17852-v2.patch,
> HBASE-17852-v3.patch, HBASE-17852-v4.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
