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 2022/01/05 15:09:00 UTC
[jira] [Commented] (HBASE-26611) Changing SFT implementation on disabled table is dangerous
[ https://issues.apache.org/jira/browse/HBASE-26611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469378#comment-17469378 ]
Wellington Chevreuil commented on HBASE-26611:
----------------------------------------------
Is this really possible? Wouldn't the MIGRATION SFT kick in once the table is finally enabled and its regions reopened?
> Changing SFT implementation on disabled table is dangerous
> ----------------------------------------------------------
>
> Key: HBASE-26611
> URL: https://issues.apache.org/jira/browse/HBASE-26611
> Project: HBase
> Issue Type: Sub-task
> Components: HFile, proc-v2
> Reporter: Duo Zhang
> Priority: Critical
>
> As our current design is to have a MIGRATION SFT so when region opens, we will mirror the store files to the dst SFT.
> But for a disabled table, the region will not be reopened so we have no chance to mirror the store files list, so after user enable the table, it may find out that all the store files are gone...
--
This message was sent by Atlassian Jira
(v8.20.1#820001)