[jira] [Commented] (HBASE-25548) Optionally allow snapshots to preserve cluster's max filesize config by setting it into table descriptor
[
https://issues.apache.org/jira/browse/HBASE-25548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17322506#comment-17322506
]
Hudson commented on HBASE-25548:
Results for branch branch-2.2
[build #205 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/205/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/205//General_Nightly_Build_Report/]
(x) {color:red}-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.2/205//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-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.2/205//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/205//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> 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)
[jira] [Commented] (HBASE-25548) Optionally allow snapshots to preserve cluster's max filesize config by setting it into table descriptor
[
https://issues.apache.org/jira/browse/HBASE-25548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304491#comment-17304491
]
Hudson commented on HBASE-25548:
Results for branch branch-2.2
[build #192 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/192/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/192//General_Nightly_Build_Report/]
(x) {color:red}-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.2/192//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {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.2/192//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/192//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> 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)
[jira] [Commented] (HBASE-25548) Optionally allow snapshots to preserve cluster's max filesize config by setting it into table descriptor
[
https://issues.apache.org/jira/browse/HBASE-25548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299780#comment-17299780
]
Hudson commented on HBASE-25548:
Results for branch branch-2
[build #198 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/198/]:
(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/198/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/198/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/198/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/198/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)
[jira] [Commented] (HBASE-25548) Optionally allow snapshots to preserve cluster's max filesize config by setting it into table descriptor
[
https://issues.apache.org/jira/browse/HBASE-25548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299752#comment-17299752
]
Hudson commented on HBASE-25548:
Results for branch branch-2.3
[build #183 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/183/]:
(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.3/183/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.3/183/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.3/183/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.3/183/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)
[jira] [Commented] (HBASE-25548) Optionally allow snapshots to preserve cluster's max filesize config by setting it into table descriptor
[
https://issues.apache.org/jira/browse/HBASE-25548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17299470#comment-17299470
]
Hudson commented on HBASE-25548:
Results for branch master
[build #233 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/233/]:
(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/master/233/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/233/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/master/233/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)
[jira] [Commented] (HBASE-25548) Optionally allow snapshots to preserve cluster's max filesize config by setting it into table descriptor
[
https://issues.apache.org/jira/browse/HBASE-25548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
