[
https://issues.apache.org/jira/browse/HBASE-26718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513809#comment-17513809
]
Hudson commented on HBASE-26718:
--------------------------------
Results for branch branch-2
[build #502 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/502/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/502/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/502/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/502/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/502/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}
> HFileArchiver can remove referenced StoreFiles from the archive
> ---------------------------------------------------------------
>
> Key: HBASE-26718
> URL: https://issues.apache.org/jira/browse/HBASE-26718
> Project: HBase
> Issue Type: Bug
> Components: Compaction, HFile, snapshots
> Affects Versions: 0.95.0, 1.0.0, 3.0.0-alpha-1, 2.0.0
> Reporter: David Manning
> Assignee: David Manning
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-3, 2.4.12
>
>
> There is a comment in {{HFileArchiver#resolveAndArchiveFile}}:
> {code:java}
> // if the file already exists in the archive, move that one to a timestamped
> backup. This is a
> // really, really unlikely situtation, where we get the same name for the
> existing file, but
> // is included just for that 1 in trillion chance.
> {code}
> In reality, we did encounter this frequently enough to cause problems. More
> details will be included and linked in a separate issue.
> But regardless of how we get into this situation, we can consider a different
> approach to solving it. If we assume store files are immutable, and a store
> file with the same name and location already exists in the archive, then it
> can be safer to assume the file was already archived successfully, and react
> accordingly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
