You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2021/02/03 17:01:00 UTC

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

Wellington Chevreuil created HBASE-25548:
--------------------------------------------

             Summary: Optionally allow snapshots to preserve cluster's max filesize config by setting it into table descriptor  
                 Key: HBASE-25548
                 URL: https://issues.apache.org/jira/browse/HBASE-25548
             Project: HBase
          Issue Type: Improvement
            Reporter: Wellington Chevreuil
            Assignee: Wellington Chevreuil


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.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)