[
https://issues.apache.org/jira/browse/HBASE-28140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28140.
-------------------------------
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to master and branch-3.
Thanks [~GeorryHuang] [~Xiaolin Ha] [~wchevreuil] for reviewing!
> 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)
