You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2022/08/17 19:43:00 UTC
[jira] [Updated] (HBASE-26969) Eliminate MOB renames when SFT is enabled
[ https://issues.apache.org/jira/browse/HBASE-26969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-26969:
---------------------------------
Fix Version/s: 2.6.0
2.5.1
(was: 2.5.0)
> Eliminate MOB renames when SFT is enabled
> -----------------------------------------
>
> Key: HBASE-26969
> URL: https://issues.apache.org/jira/browse/HBASE-26969
> Project: HBase
> Issue Type: Sub-task
> Components: mob
> Affects Versions: 2.5.0, 3.0.0-alpha-3
> Reporter: Szabolcs Bukros
> Assignee: Szabolcs Bukros
> Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4
>
>
> MOB file compaction and flush still relies on renames even when SFT is enabled.
> My proposed changes are:
> * when requireWritingToTmpDirFirst is false during mob flush/compact instead of using the temp writer we should create a different writer using a {color:#000000}StoreFileWriterCreationTracker that writes directly to the mob store folder{color}
> * {color:#000000}these StoreFileWriterCreationTracker should be stored in the MobStore. This would requires us to extend MobStore with a createWriter and a finalizeWriter method to handle this{color}
> * {color:#000000}refactor {color}MobFileCleanerChore to run on the RS instead on Master to allow access to the {color:#000000}StoreFileWriterCreationTracker{color}s to make sure the currently written files are not cleaned up
--
This message was sent by Atlassian Jira
(v8.20.10#820010)