[
https://issues.apache.org/jira/browse/HBASE-25548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299234#comment-17299234
]
Hudson commented on HBASE-25548:
--------------------------------
Results for branch branch-2.4
[build #69 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/69/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/69/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/69/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/69/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/69/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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)
