[
https://issues.apache.org/jira/browse/HBASE-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HBASE-4402:
-------------------------------
Attachment: hbase-4402.txt
New patch addresses Ted's comments. The log messages are as follows:
For the case where all are retained:
{code}
2011-09-15 11:22:57,592 INFO [main] master.DefaultLoadBalancer(643):
Reassigned 100 regions. 100 retained the pre-restart assignment.
{code}
For the case where some were reassigned:
{code}
2011-09-15 11:22:57,604 INFO [main] master.DefaultLoadBalancer(643):
Reassigned 100 regions. 80 retained the pre-restart assignment. 20 regions were
assigned to random hosts, since the old hosts for these regions are no longer
present in the cluster. These hosts were:
server29568
server80916
{code}
> 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, 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
