ndimiduk commented on PR #6370: URL: https://github.com/apache/hbase/pull/6370#issuecomment-2446258976
> When we go to restore this cluster, it'll pull the full backup and the 2 incrementals. The full backup will get restored first, so the new table will have regions A, B, C. Targeting the original split boundaries means making more work for the region servers as the regions load up and then hit their split thresholds. Actually, what happens if the region partition points change while the restore is happening? Say you restore the full backup, and the first incremental. The regions get too big and split. Now the second incremental is being restored, but the region partitions have changed. Instead of targeting the old region partitions, which we know have changed (i.e., due to increased data volume), what if the restore process targets the region partitions of the most recent incremental backup -- G, H, I, J, K, L, from your example. I guess the splitting process is really challenging and slow? -- 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: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
