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 2020/06/18 01:38:00 UTC
[jira] [Commented] (HBASE-24582) The current implementation of
assignMetaReplicas() may assign replica meta regions to the same server
hosting primary meta region.
[ https://issues.apache.org/jira/browse/HBASE-24582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138943#comment-17138943 ]
Duo Zhang commented on HBASE-24582:
-----------------------------------
It could also double assign a region and cause problem...
> The current implementation of assignMetaReplicas() may assign replica meta regions to the same server hosting primary meta region.
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-24582
> URL: https://issues.apache.org/jira/browse/HBASE-24582
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Huaxiang Sun
> Assignee: Huaxiang Sun
> Priority: Major
>
> We need to take the approach similar to SplitTableRegionProcedure, which uses round robin algo to assign replica regions and excludes the primary server.
>
> {code:java}
> return AssignmentManagerUtil.createAssignProceduresForOpeningNewRegions(env, hris,
> getRegionReplication(env), getParentRegionServerName(env));{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)