[
https://issues.apache.org/jira/browse/HBASE-14141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654894#comment-15654894
]
Enis Soztutar commented on HBASE-14141:
---------------------------------------
bq. We already depend on WALs for incremental backup. If WAL is unreliable so
is HBase. Backup can't be more reliable than WAL/HBase.
Not sure whether I understand what you are saying. The above paragraph is not
talking about WAL being unreliable, but the fact that we cannot design the
backup to depend on writing some metadata reliably on WAL close. writing to WAL
and writing metadata to backup table on WAL close are very different things.
bq. No. In this case, default mode is the way to go (what we have now).
Why are we complicating the design with two different modes, and switching and
everything. How will any user chose which one to use? I think we should stick
to a single mode / solution that will work for most of the cases rather than
complicating the life of the user and also maintaining the backup code for two
different code paths.
> HBase Backup/Restore Phase 3: Filter WALs on backup to include only edits
> from backup tables
> --------------------------------------------------------------------------------------------
>
> Key: HBASE-14141
> URL: https://issues.apache.org/jira/browse/HBASE-14141
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 2.0.0
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Labels: backup
> Fix For: 2.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
