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 2025/07/04 09:49:00 UTC
[jira] [Updated] (HBASE-29292) Revise TestRecreateCluster
[ https://issues.apache.org/jira/browse/HBASE-29292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-29292:
------------------------------
Fix Version/s: 3.0.0-beta-2
(was: 3.0.0)
(was: 4.0.0-alpha-1)
> Revise TestRecreateCluster
> --------------------------
>
> Key: HBASE-29292
> URL: https://issues.apache.org/jira/browse/HBASE-29292
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0, 4.0.0-alpha-1, 2.7.0
> Reporter: Tak-Lon (Stephen) Wu
> Assignee: Tak-Lon (Stephen) Wu
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> -Split from HBASE-24282 and based on HBASE-24833, we would like to continue the attempt mentioned in [https://github.com/apache/hbase/pull/2114] and introduce a feature flag {{hbase.master.assign.regions.on.unknown.servers}} to control this recovery when regions are startup at unknown servers.-
> TestRecreateCluster has a logic error and and would cleanup the master region in the root directory, this is not the right case we would like to support in the cloud storage that we expect the hbase cluster to shutdown gracefully and master region to be flushed to permanent storage as HFiles.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)