[
https://issues.apache.org/jira/browse/HBASE-28140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775276#comment-17775276
]
Hudson commented on HBASE-28140:
--------------------------------
Results for branch master
[build #927 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/927/]:
(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/master/927/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/918/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/master/927/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}
> AbstractWALProvider may miss the WAL which is under creation in getWALs method
> ------------------------------------------------------------------------------
>
> Key: HBASE-28140
> URL: https://issues.apache.org/jira/browse/HBASE-28140
> Project: HBase
> Issue Type: Bug
> Components: Replication, wal
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-beta-1
>
>
> Found this problem when analysis HBASE-28114.
> In the AbstractFSWALProvider implementation, if wal field is null, we will
> acquire the creation lock so we can get the WAL instance which is under
> creation, so we will not miss the WAL instance, and also will not get an
> uninitialized WAL instance.
> We should try to do the same for remote WAL, otherwise the logic in
> WALEntryStream, where we rely on the return value of getWALs to test whether
> a WAL file is currently being written, will be broken.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
