[
https://issues.apache.org/jira/browse/HBASE-29519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014695#comment-18014695
]
Vinayak Hegde commented on HBASE-29519:
---------------------------------------
Thanks [~andor] for reviewing. Just one clarifying question:
{quote}Bulkload files are probably in a safe place already (S3) and in case of
a disaster, user should be able to manually restore them in an optimal way.
{quote}
Do you mean that the user would have a separate copy of the generated HFiles
stored somewhere, which can then be used during restore?
I also have a follow-up scenario:
Suppose the user initially didn’t enable this configuration and performed a few
bulk-loads. Later, they enabled it (perhaps because another replication peer
required it). Since this is a global configuration, continuous backup will then
start copying bulk-loaded files.
In this case, during restore, the user would need to remember that the first
few bulk-loads are not covered and must be restored manually, while the later
ones are covered by continuous backup.
is this okay or acceptable?
> Copy Bulkloaded Files in Continuous Backup
> ------------------------------------------
>
> Key: HBASE-29519
> URL: https://issues.apache.org/jira/browse/HBASE-29519
> Project: HBase
> Issue Type: Sub-task
> Components: backup&restore
> Reporter: Vinayak Hegde
> Assignee: Vinayak Hegde
> Priority: Major
> Labels: pull-request-available
>
> Enhance the continuous backup replication endpoint to detect bulkload
> operations and copy their HFiles to the backup location (e.g., S3).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
