[
https://issues.apache.org/jira/browse/HBASE-29662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035802#comment-18035802
]
Hudson commented on HBASE-29662:
--------------------------------
Results for branch branch-2
[build #1344 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1344/]:
(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/1344/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/1344/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/1344/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/1344/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1344/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {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/1344/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/1344/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1344/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk17 hadoop 3.4.1 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1344/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test for HBase 2 {color}
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.2 {color}
> Reading data via TableSnapshotInputFormat should fail instead of reading no
> data if restore directory got deleted
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-29662
> URL: https://issues.apache.org/jira/browse/HBASE-29662
> Project: HBase
> Issue Type: Bug
> Components: snapshots
> Reporter: Ujjawal Kumar
> Assignee: Prathyusha
> Priority: Critical
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 3.0.0-beta-2, 2.6.4, 2.5.13
>
>
> We observed an issue in our production where data read via
> TableSnapshotInputFormat was empty even though the snapshot had actual data.
> The sequence of events look like this :
> 1. Snapshot was restored into a temp directory via
> RestoreSnapshotHelper.copySnapshotForScanner (via
> TableMapReduceUtil.initTableSnapshotMapperJob) as part of job submission
> 2. The temp directory was deleted by another process
> 3. Within mapper, HRegion were created on top of temp directory.
> HRegionFileSystem#checkRegionInfoOnFilesystem was called to check regioninfo,
> *it didn't find region level directory and recreated an empty one !*
> Due to this, the MR job didn't read any data but was considered successful.
> *The correct behavior would be to ensure that mapper fails if temp directory
> doesn't exist*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
