vinayakphegde commented on PR #7445: URL: https://github.com/apache/hbase/pull/7445#issuecomment-3532879396
> > > 3. If we have normal replication enabled (a normal replication peer), will all CFs with REPLICATION_SCOPE = 1 also be targeted for this PITR? > > > > > > Negative. Continuous backup needs a special replication endpoint to be set for the peer `ContinuousBackupReplicationEndpoint`. Normal replication peers are not affected and work fine side-by-side. > > How does the PITR Endpoint avoids backing up entries for CFs with REPLICATION_SCOPE set to true (for normal replication), but which are not primarily wanted to be in PITR backups? Is it possible to "opt out" from PITR at CF table/level? @wchevreuil That is determined when starting the continuous backup. For example, if you want to start continuous backup for table1, you initiate a full backup with the continuous backup option enabled. This performs the full backup and adds the table to the continuous_backup_replication_peer (the default replication peer used for continuous backup). If the column families don’t already have replication scope enabled, it’s also set to true at this stage. Please refer to the following methods for details: https://github.com/apache/hbase/blob/6aa212f5abe3b1556740c3e7e80a4761d21a1c15/hbase-backup/src/main/java/org/apache/hadoop/hbase/backup/impl/FullTableBackupClient.java#L269 enableTableReplication() updateContinuousBackupReplicationPeer() addContinuousBackupReplicationPeer() So, if you manually change the replication scope to true for a random table, it will not be replicated as part of the continuous backup, since it’s not included in the continuous_backup_replication_peer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
