You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/01/10 15:25:00 UTC
[jira] [Created] (HBASE-19752)
RSGroupBasedLoadBalancer#getMisplacedRegions() should handle the case where
rs group cannot be determined
Ted Yu created HBASE-19752:
------------------------------
Summary: RSGroupBasedLoadBalancer#getMisplacedRegions() should handle the case where rs group cannot be determined
Key: HBASE-19752
URL: https://issues.apache.org/jira/browse/HBASE-19752
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Observed the following in rs group test output:
{code}
2018-01-10 14:17:23,006 DEBUG [AssignmentThread] rsgroup.RSGroupBasedLoadBalancer(316): Found misplaced region: hbase:acl,,1515593841277.ecf47ecb7522d7fab40db0a237f973fd. on server: localhost,1,1 found in group: null outside of group: UNKNOWN
{code}
Here is corresponding code:
{code}
if (assignedServer != null &&
(info == null || !info.containsServer(assignedServer.getAddress()))) {
RSGroupInfo otherInfo = null;
otherInfo = rsGroupInfoManager.getRSGroupOfServer(assignedServer.getAddress());
LOG.debug("Found misplaced region: " + regionInfo.getRegionNameAsString() +
{code}
As you can see, both info and otherInfo were null.
In this case, the region should not be placed in misplacedRegions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)