[
https://issues.apache.org/jira/browse/HBASE-29238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945666#comment-17945666
]
Hudson commented on HBASE-29238:
--------------------------------
Results for branch branch-2
[build #1259 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259//console].
(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 source release artifact{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259//console].
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1259//console].
> ExportSnapshot support specify storage policy
> ---------------------------------------------
>
> Key: HBASE-29238
> URL: https://issues.apache.org/jira/browse/HBASE-29238
> Project: HBase
> Issue Type: Improvement
> Components: snapshots
> Reporter: Reid Chan
> Assignee: Reid Chan
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.3
>
>
> If storage policy is unspecified, the default is either HOT or DISK.
> In our production case, we have a cluster which support DISK in A IDC while
> SSD only in B IDC (yes, it is cross-IDC cluster).
> We want to export a snapshot to B IDC using all SSD directly, but since
> default policy, it will be DISK. We have to trigger a major compaction to
> move all data from DISK to SSD which it is time consuming.
> That's the background of this improvement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
