[
https://issues.apache.org/jira/browse/HBASE-25891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mallikarjun updated HBASE-25891:
--------------------------------
Description:
Currently WAL logs are stored in `backup:system` meta table
{code:java}
// code placeholder
{code}
#
# Ever growing rows of wal's sourced for incremental backup is maintained and
never cleaned up.
# Unnecessary to have wal log listed for performing incremental backup or log
cle
was:
Here are some of the problems identified.
1. Ever growing rows of wal's sourced for incremental backup is maintained and
never cleaned up.
2. Backup sessions, Backup sets, wal logs, active sessions, merges, etc are all
identified by prefix of row key. Which doesn't seem to be very intuitive
> Remove the dependence of storing WAL filenames for incremental backup
> ---------------------------------------------------------------------
>
> Key: HBASE-25891
> URL: https://issues.apache.org/jira/browse/HBASE-25891
> Project: HBase
> Issue Type: Improvement
> Components: backup&restore
> Reporter: Mallikarjun
> Assignee: Mallikarjun
> Priority: Major
>
> Currently WAL logs are stored in `backup:system` meta table
>
> {code:java}
> // code placeholder
> {code}
>
>
>
> #
> # Ever growing rows of wal's sourced for incremental backup is maintained
> and never cleaned up.
> # Unnecessary to have wal log listed for performing incremental backup or
> log cle
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
