[
https://issues.apache.org/jira/browse/HBASE-26322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555595#comment-17555595
]
Mallikarjun edited comment on HBASE-26322 at 6/17/22 1:25 PM:
--------------------------------------------------------------
Backup currently doesn't understand rsgroups. Which results into 2 problems.
Say there are 2 rsgroups. RsgroupA, RsgroupB. tableA is part of RsgroupA and
tableB is part of RsgroupB. rs1A, rs2A, rs3A regionservers are part of
RsgroupA. rs1B, rs2B, rs3B regionserver are part of rsgroupB.
Problem 1:
When you enable backup on tableA, then only rs1A, rs2A, rs3A should participate
in backup (WAL's of these regionservers are backed up). Since backup doesn't
understand rsgroup, all regionservers participate in backup rs1A, rs2A, rs3A,
rs1B, rs2B, rs3B. Which means, you need to plan for additional capacity
requirement for additional WAL's and other problems. (Because wals are retained
until next successful backup is completed)
Problem 2:
BackupLogCleaner also doesn't understand rsgroups with incremental backup
enabled. This can result into a big problem. In the above example, say backup
is configured for only TableA. Hence BackupLogCleaner cleans up WAL's of only
rs1A, rs2A, rs3A once a backup is completed. WAL's of rs1B, rs2B, rs3B are
never cleaned up because there is no table backup configured and every growing
WAL's will fill up the disk easily (since WAL's are not compressed).
[~zhangduo] Hope this is enough details. Please ask anything you did not
understand.
P.S: Thank you very much for taking time to look into this.
was (Author: rda3mon):
Backup currently doesn't understand rsgroups. Which results into 2 problems.
Say there are 2 rsgroups. RsgroupA, RsgroupB. tableA is part of RsgroupA and
tableB is part of RsgroupB. rs1A, rs2A, rs3A regionservers are part of
RsgroupA. rs1B, rs2B, rs3B regionserver are part of rsgroupB.
Problem 1:
When you enable backup on tableA, then only rs1A, rs2A, rs3A should participate
in backup (WAL's of these regionservers are backed up). Since backup doesn't
understand rsgroup, all regionservers participate in backup rs1A, rs2A, rs3A,
rs1B, rs2B, rs3B. Which means, you need to plan for additional capacity
requirement for additional WAL's, and other problems.
Problem 2:
BackupLogCleaner also doesn't understand rsgroups with incremental backup
enabled. This can result into a big problem. In the above example, say backup
is configured for only TableA. Hence BackupLogCleaner cleans up WAL's of only
rs1A, rs2A, rs3A once a backup is completed. WAL's of rs1B, rs2B, rs3B are
never cleaned up because there is no table backup configured and every growing
WAL's will fill up the disk easily (since WAL's are not compressed).
[~zhangduo] Hope this is enough details. Please ask anything you did not
understand.
P.S: Thank you very much for taking time to look into this.
> Add rsgroup support for Backup
> ------------------------------
>
> Key: HBASE-26322
> URL: https://issues.apache.org/jira/browse/HBASE-26322
> Project: HBase
> Issue Type: Improvement
> Components: backup&restore
> Affects Versions: 3.0.0-alpha-2
> Reporter: Mallikarjun
> Assignee: Mallikarjun
> Priority: Minor
> Fix For: 3.0.0-alpha-4
>
>
> There are some places where backup needs some changes with respect to
> rsgroup. Some of them being addressed here are
> # Incremental backup wal backup should happen only for servers which are
> part of a particular rsgroup under which namespace is configured for table
> backup under consideration
> # BackupLogCleaner should keep references only from those servers which are
> part of a particular rsgroup under which namesapce is configured for table
> backup under consideration
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
