[
https://issues.apache.org/jira/browse/HBASE-26271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422202#comment-17422202
]
Szabolcs Bukros commented on HBASE-26271:
-----------------------------------------
[~zhangduo] Created a PR with my initial changes. Could you please take a look?
[~wchevreuil] suggested that if we could list the currently written compaction
targets we could add that to the check and should not solely rely on the
leftover file ttl to prevent breaking a long-running compaction. I have not
found a nice way to add a generic implementation for this so my initial
solution is limited to the {color:#000000}DirectStoreCompactor. What do you
think?
{color}
{color:#000000}I'm planning to add metrics to get a clearer idea of chore
performance/results and extend the api to get this info in a followup
commit.{color}
> 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)
