[
https://issues.apache.org/jira/browse/HBASE-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105378#comment-13105378
]
Ted Yu commented on HBASE-4402:
-------------------------------
{code}
+ ServerName randomServer = servers.get(RANDOM.nextInt(servers.size()));
+ assignments.get(randomServer).add(region);
+ numRandomAssignments++;
{code}
I think we should log the (region, server) pairs for the above case.
> Retaining locality after restart broken
> ---------------------------------------
>
> Key: HBASE-4402
> URL: https://issues.apache.org/jira/browse/HBASE-4402
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.92.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.92.0
>
> Attachments: hbase-4402.txt
>
>
> In DefaultLoadBalancer, we implement the "retain assignment" function like so:
> {code}
> if (sn != null && servers.contains(sn)) {
> assignments.get(sn).add(region.getKey());
> {code}
> but this will never work since after a cluster restart, all servers have a
> new ServerName with a new startcode.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
