You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2024/03/19 15:35:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Bryan Beaudreault updated HBASE-26611:
--------------------------------------
Fix Version/s: 2.5.0
(was: 2.6.0)
> 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
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 2.5.0, 3.0.0-alpha-3
>
>
> 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.10#820010)