[ 
https://issues.apache.org/jira/browse/HBASE-26187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608889#comment-17608889
 ] 

Bryan Beaudreault edited comment on HBASE-26187 at 9/23/22 7:10 PM:
--------------------------------------------------------------------

I couldn't really find a discussion on this topic, just a single idea sentence. 
I know it's been a while, but what happens if merge/split fails? Would it leave 
files in place which might cause issues if the region is moved and re-opened 
elsewhere? That's one reason I could imagine wanting a tmp dir, is you have a 
single atomic operation at the end to load them in.

[~zhangduo] [~wchevreuil] 


was (Author: bbeaudreault):
I couldn't really find a discussion on this topic, just a single idea sentence. 
I know it's been a while, but what happens if merge/split fails? Would it leave 
files in place which might cause issues if the region is moved and re-opened 
elsewhere? That's one reason I could imagine wanting a tmp dir, is you have a 
single atomic operation at the end to load them in.

> Write straight into the store directory when Splitting and Merging
> ------------------------------------------------------------------
>
>                 Key: HBASE-26187
>                 URL: https://issues.apache.org/jira/browse/HBASE-26187
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 3.0.0-alpha-1
>            Reporter: Wellington Chevreuil
>            Assignee: Wellington Chevreuil
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-2
>
>
> As discussed with [~zhangduo] on HBASE-26079, we think there's no actual need 
> for Splits/Merges to make use of temp directories, because the split/merge 
> region files would not be loaded until the new regions are ready to open, 
> meaning the split/merge operation has completed. This would then avoid the 
> need for a FS rename at the end of split/merge operation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to