[ https://issues.apache.org/jira/browse/HBASE-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120680#comment-13120680 ]
stack commented on HBASE-4402: ------------------------------ Ran test suite w/o on 0.92 and all tests passed and with it these failed: {code} Failed tests: testOnlineChangeTableSchema(org.apache.hadoop.hbase.client.TestAdmin) testForceSplit(org.apache.hadoop.hbase.client.TestAdmin): expected:<2> but was:<1> testForceSplitMultiFamily(org.apache.hadoop.hbase.client.TestAdmin): expected:<2> but was:<1> Tests in error: testMergeTable(org.apache.hadoop.hbase.util.TestMergeTable): test timed out after 300000 milliseconds {code} I'm taking a look. > 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. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira