[
https://issues.apache.org/jira/browse/HBASE-26271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415828#comment-17415828
]
Duo Zhang commented on HBASE-26271:
-----------------------------------
I'm not familiar with Accumulo but I guess the approach you describe here is to
solve the 'compact away' scenario in HBase? The file which have been compacted
away may still be referenced in scan, so we can not delete them immediately,
and we also need a place to store the list in case of region server crash or
region reassign. The solution for this in HBase is implemented by [~zghao],
where we store the compacted away file list in the final output file's
metadata, so when reopening the region, we know which files should be deleted.
In general, I do not think this could solve the 'flush/compaction fails'
problem. In fact, even if we add a list in store file tracker to record these
files, we could still fail before inserting these files into store file tracker
right? But the files are already there and need to be deleted. So FWIW, we
still need to list the filesystem to find them out...
WDYT?
Thanks.
> Cleanup the broken store files under data directory
> ---------------------------------------------------
>
> Key: HBASE-26271
> URL: https://issues.apache.org/jira/browse/HBASE-26271
> Project: HBase
> Issue Type: Sub-task
> Components: HFile
> Reporter: Duo Zhang
> Priority: Major
>
> As for some new store file tracker implementation, we allow flush/compaction
> to write directly to data directory, so if we crash in the middle, there will
> be broken store files left in the data directory.
> We should find a proper way to delete these broken files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
