[HBASE-25548] Optionally allow snapshots to preserve cluster's max filesize config by setting it into table descriptor

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 2.3.4, 2.5.0, 2.4.2
• Fix Version/s: 3.0.0-alpha-1, 2.5.0, 2.3.5, 2.4.3
• Assignee: Wellington Chevreuil
• Reporter: Wellington Chevreuil
• Created: 03/Feb/21 17:00
• Updated: 15/Apr/21 22:07
• Resolved: 10/Mar/21 10:56

Description

While using snapshots for data migration, if the source cluster has non-default definition for hbase.hregion.max.filesize, table being snapshotted doesn't have MAX_FILESIZE attribute set, then if snapshot is exported to a separate cluster with different value for hbase.hregion.max.filesize, any cloned table will not respect the original value. In cases where the original cluster had a much larger value set to hbase.hregion.max.filesize then the destination cluster, restoring snapshot can trigger a storm of splits.

This Jira introduces an optional configuration (disabled by default) that allows for the hbase.hregion.max.filesize value to be saved within the table MAX_FILESIZE descriptor at snapshot creation time.

 

Issue Links

• links to: GitHub Pull Request #2923