[
https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215502#comment-16215502
]
Yi Liang edited comment on HBASE-18352 at 10/23/17 5:36 PM:
------------------------------------------------------------
I saw another situation that may cause random assignment. When we restart
hbase, if we start master first, and then region servers.
Once one region server count in, master will start to begin region assignment.
There is a possibility that the assign plan is created for a region before its
last region server up, so AM will randomly chose one region servers for this
region.
And if we restart all rs before master, we will not see above issues.
was (Author: easyliangjob):
I saw another situation that may cause random assignment. When we restart
hbase, if we start master first, and then regionservers.
Once one region server count in, master will start to begin region assignment.
There is a possibility that the assign plan is created for a region before its
last region server up, so AM will randomly chose one region servers for this
region.
> Enable Replica tests that were disabled by Proc-V2 AM in HBASE-14614
> --------------------------------------------------------------------
>
> Key: HBASE-18352
> URL: https://issues.apache.org/jira/browse/HBASE-18352
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 2.0.0-alpha-1
> Reporter: Stephen Yuan Jiang
> Assignee: huaxiang sun
>
> The following replica tests were disabled by Core Proc-V2 AM in HBASE-14614:
> - Disabled parts of...testCreateTableWithMultipleReplicas in
> TestMasterOperationsForRegionReplicas There is an issue w/ assigning more
> replicas if number of replicas is changed on us. See '/* DISABLED!!!!! FOR
> NOW!!!!'.
> - Disabled testRegionReplicasOnMidClusterHighReplication in
> TestStochasticLoadBalancer2
> - Disabled testFlushAndCompactionsInPrimary in TestRegionReplicas
> This JIRA tracks the work to enable them (or modify/remove if not applicable).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)