You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/01/16 13:27:00 UTC

[jira] [Updated] (HBASE-26640) Reimplement master location region initialization to better work with SFT

     [ https://issues.apache.org/jira/browse/HBASE-26640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang updated HBASE-26640:
------------------------------
    Summary: Reimplement master location region initialization to better work with SFT  (was: The master local region should not be effected by the global SFT configuration change)

> Reimplement master location region initialization to better work with SFT
> -------------------------------------------------------------------------
>
>                 Key: HBASE-26640
>                 URL: https://issues.apache.org/jira/browse/HBASE-26640
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master, RegionProcedureStore
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>
> It is not like a normal region where we have a TableDescriptor so it can store the SFT implementation of its own. In the current implementation, if we change the global SFT configuration, the SFT implementation of the master local reigon will be changed and cause data loss.
> First I think we could hard coded it to use DefaultSFT. The region is small and will not cause too much performance impact. Then we could find a way to manage the SFT implementation of it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)