[ https://issues.apache.org/jira/browse/HBASE-18575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Umesh Agashe updated HBASE-18575: --------------------------------- Status: Patch Available (was: In Progress) * Fixed ServerCrashProcedure to set forceNewPlan to false for instances AssignProcedure. This enables balancer to find most suitable target server * Fixed and enabled TestRestartCluster#testRetainAssignmentOnRestart on master * Renamed method ServerName@isSameHostnameAndPort() to isSameAddress() > [AMv2] Enable and fix TestRestartCluster#testRetainAssignmentOnRestart on > master > -------------------------------------------------------------------------------- > > Key: HBASE-18575 > URL: https://issues.apache.org/jira/browse/HBASE-18575 > Project: HBase > Issue Type: Bug > Components: amv2 > Affects Versions: 2.0.0 > Reporter: Umesh Agashe > Assignee: Umesh Agashe > Priority: Critical > Fix For: 2.0.0 > > Attachments: hbase-18575.master.001.patch > > > * Test creates 3 node cluster (master + 2 RS) and creates 3 tables with 1 > region each. > * It then takes a snapshot of region assignments > * Shuts down the cluster and restarts with 4 nodes (2 RS on same ports, 1 RS > on port where master was running previously and master on new port) > * Takes snapshot of region assignments > * Expected behavior is regions will be retained on RS with appropriate ports > Debugging done so far shows that, when cluster is restarted meta is loaded > but meta has old entries (though the ports are same for RSs, start timestamps > are different). AssignmentManager#processofflineServersWithOnlineRegions() > finds that old RS with different timestamps are not online even though > regions assigned to them are online; triggering submitting SCP for each those > RSs. Subprocedure AssignProcedure of SCP has forceNewPlan set to true. Which > triggers re-assignment of regions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)