[
https://issues.apache.org/jira/browse/HBASE-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093947#comment-16093947
]
Umesh Agashe edited comment on HBASE-18366 at 7/19/17 11:36 PM:
----------------------------------------------------------------
bq. there is a RS with highest version coming in. We should move all system
tables to this new RS
Concern here is if one new node with higher version is added to the cluster,
all system table regions will be moved to this node. Subsequent addition of new
nodes with same version as previous one will not have any affect but these
regions will only be moved (if at all) by load balancer or by user.
was (Author: uagashe):
bq. there is a RS with highest version coming in. We should move all system
tables to this new RS
Concern here is if one new node is added to the cluster, all system table
regions will be moved to this node. Subsequent addition of new nodes will not
have any affect but these regions will only be moved (if at all) by load
balancer or by user.
> Fix flaky test
> hbase.master.procedure.TestServerCrashProcedure#testRecoveryAndDoubleExecutionOnRsWithMeta
> ---------------------------------------------------------------------------------------------------------
>
> Key: HBASE-18366
> URL: https://issues.apache.org/jira/browse/HBASE-18366
> Project: HBase
> Issue Type: Bug
> Reporter: Umesh Agashe
> Assignee: Umesh Agashe
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: hbase-18366.fix1.patch, hbase-18366.fix2.patch
>
>
> It worked for a few days after enabling it with HBASE-18278. But started
> failing after commits:
> 6786b2b
> 68436c9
> 75d2eca
> 50bb045
> df93c13
> It works with one commit before: c5abb6c. Need to see what changed with those
> commits.
> Currently it fails with TableNotFoundException.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
