[
https://issues.apache.org/jira/browse/HBASE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16215037#comment-16215037
]
ramkrishna.s.vasudevan commented on HBASE-18352:
------------------------------------------------
{code}
LOG.info("Processing expiration of " + serverName + " on " +
this.master.getServerName());
master.getAssignmentManager().submitServerCrash(serverName, true);
{code}
These things while cluster is joining seems to be a problem. We have already
shutdown the cluster but why are we explicity processing expireServer? Will be
back 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)
