[
https://issues.apache.org/jira/browse/HBASE-26322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558775#comment-17558775
]
Duo Zhang commented on HBASE-26322:
-----------------------------------
For #1, the region server's in rs group can be changed, so how do you make sure
that a region server will is not currently in the rs group of this table does
not have WAL for this table? Maybe there were regions of this table on the
region server is the past? And also, now we have some fallback logic to make
sure that even there is no region server in the group, we can still make the
regions configured in this group online. How do you deal with this scenario?
For #2, I'm a bit confused. When we do backup, we will not consider rs group,
but when we do cleanup, we will consider rs group?
Thanks.
> 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)
