[
https://issues.apache.org/jira/browse/HBASE-25548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil resolved HBASE-25548.
------------------------------------------
Resolution: Fixed
Thanks for the review, [~psomogyi]! Merged to master, branch-2, branch-2.4 and
branch-2.3. I'll open a backport Jira for branch-2.2, as the cherrypick for
that branch is conflicting.
> 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
> Affects Versions: 3.0.0-alpha-1, 2.3.4, 2.5.0, 2.4.2
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.3.5, 2.4.3
>
>
> 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)
