hgromer commented on PR #6370:
URL: https://github.com/apache/hbase/pull/6370#issuecomment-2569273461
> Come to think of it, I believe that there's a flag to disable
splits/merges of regions for a table. Whichever strategy we pursue, should the
restore system use that flag to take a lock on the region boundaries before it
starts rewriting data?
I think this would be an improvement to the current system. From my
understanding, it seems that in order to disable region splits + merges at the
table level, we'd have to modify the TBD.
For merges, we can do `TBD#setMergeEnabled(false)`. However, for splits, it
seems we'd need to do something like
`TBD#setValue("hbase.hregion.max.filesize", String.valueOf(Long.MAX_VALUE))`.
This means we also need to re-set the descriptor once we've finished the
restore process.
It seems we can also disable splits + merges for the whole cluster via the
HMaster. I think if we wanted something like the HMaster switch, at a
table-level, we'd need to build something new.
Do you mind if I tackle this in a follow-up PR?
--
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]
