[
https://issues.apache.org/jira/browse/HBASE-27519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenglei updated HBASE-27519:
-----------------------------
Status: Patch Available (was: Open)
> Another case for FNFE on StoreFileScanner after a flush followed by a
> compaction
> --------------------------------------------------------------------------------
>
> Key: HBASE-27519
> URL: https://issues.apache.org/jira/browse/HBASE-27519
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.5.2, 2.4.15, 3.0.0-alpha-3, 2.6.0
> Reporter: chenglei
> Assignee: chenglei
> Priority: Major
>
> Besides the fix for {{HStore.getScanners}} for FNFE on StoreFileScanner after
> a flush followed by a compaction in HBASE-27484, there is a another case
> would cause FNFE:
> # When {{StoreScanner}} is scanning, there is a flush followed by a
> compaction. When the flushed is completed in {{HStore.completeFlush}} and
> after it adds the new {{HStoreFile}} in {{StoreEngine}}, it would notify the
> {{StoreScanner}} by {{StoreScanner.updateReaders}} with the new flushed
> {{HStoreFile}}：
> {code:java}
> public void updateReaders(List<HStoreFile> sfs, List<KeyValueScanner>
> memStoreScanners) {
> ...
> }
> {code}
> # But if before entering {{StoreScanner.updateReaders}} , the compaction task
> starts and it compacts the new flushed {{HStoreFile}} and then
> {{HStore.closeAndArchiveCompactedFiles}} is called by
> {{CompactedHFilesDischarger}} to delete the {{HStoreFile}}.
> # When {{StoreScanner.updateReaders}} continues to execute, it would read
> already deleted {{HStoreFile}} and throws FNFE.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
