[
https://issues.apache.org/jira/browse/HBASE-15372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Rodionov updated HBASE-15372:
--------------------------------------
Description:
Currently, we keep WAL file per table in backup site, this creates significant
data duplication in case of many tables in a backup set. We have to keep all
WAL files in a single place and keep track of WAL files involved per
table/backup id as links (references)
This is not only the data duplication issue, but a performance issue as well
(we copy the same file over and over again for every table in a backup set).
was:Currently, we keep WAL file per table in backup site, this creates
significant data duplication in case of many tables in a backup set. We have to
keep all WAL files in a single place and keep track of WAL files involved per
table/backup id as links (references)
> HBase Backup/Restore Phase 2: Keep WAL files in a centralized place to avoid
> duplication
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-15372
> URL: https://issues.apache.org/jira/browse/HBASE-15372
> Project: HBase
> Issue Type: Improvement
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
>
> Currently, we keep WAL file per table in backup site, this creates
> significant data duplication in case of many tables in a backup set. We have
> to keep all WAL files in a single place and keep track of WAL files involved
> per table/backup id as links (references)
> This is not only the data duplication issue, but a performance issue as well
> (we copy the same file over and over again for every table in a backup set).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
