You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Wellington Chevreuil (Jira)" <ji...@apache.org> on 2021/11/12 11:48:00 UTC
[jira] [Commented] (HBASE-26067) Change the way on how we track
store file list
[ https://issues.apache.org/jira/browse/HBASE-26067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442697#comment-17442697 ]
Wellington Chevreuil commented on HBASE-26067:
----------------------------------------------
Should we worry about HFile archiving? Currently, DeleteTable and GCRegion procedures rely on HFileArchiver to move region dirs/hfiles out of namespace/table dirs, to archive folder. Delete table, in case of large tables, can lead to lots of renames. I think changing current archiving logic to avoid rename would be challenging, as we would require some way to track archived tables/regions (maybe another status in meta or a new system table), and rewriting of existing hbck methods that rely on filesystem state to fix meta inconsistencies.
> Change the way on how we track store file list
> ----------------------------------------------
>
> Key: HBASE-26067
> URL: https://issues.apache.org/jira/browse/HBASE-26067
> Project: HBase
> Issue Type: Umbrella
> Components: HFile
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> Open a separated jira to track the work since it can not be fully included in HBASE-24749.
> I think this could be a landed prior to HBASE-24749, as if this works, we could have different implementations for tracking store file list.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)