[
https://issues.apache.org/jira/browse/HBASE-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106657#comment-16106657
]
stack commented on HBASE-18366:
-------------------------------
Why this change sir:
optional ServerName destination_server = 3;
It was required. A move w/o a destination doesn't make sense?
I like the change that foists assignment on to the balancer (by passing null)
presuming balancer will favor regionservers with higher versions....
High-level, how would you describe the change [~uagashe]? I like the bit of
having assign conscious of favoring system tables...
Patch looking good. What else is to be done?
Thanks boss.
> 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)
