[
https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214363#comment-16214363
]
huaxiang sun commented on HBASE-18352:
--------------------------------------
Posting the progress so far, testCreateTableWithMultipleReplicas failed after
enabling this test. Even with HBASE-18946, still saw the failure with the whole
cluster shutdown and comes up.
// Now shut the whole cluster down, and verify the assignments are kept
so that the
// availability constraints are met.
The issue is that when the cluster is up, it tries to retain the assignment,
and since in local unittest environment, all hostname(ip) for region server
are same, then it will try to randomly assign these regions and result in
primary/replica region being assigned to the same host. I need to check how it
works in branch-1, maybe I am missing something here.
> 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)
