hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19752) RSGroupBasedLoadBalancer#getMisplacedRegions() should handle the case where rs group cannot be determined
Date Fri, 12 Jan 2018 23:42:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-19752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16324746#comment-16324746
] 

Ted Yu commented on HBASE-19752:
--------------------------------

Commit to branch-1 was correct.
Somehow I used a partial branch-1 patch on branch-1.4

> 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
>             Fix For: 1.4.1, 1.5.0, 2.0.0-beta-1
>
>         Attachments: 19752.v1.txt, 19752.v2.txt, 19752.v3.txt, 19752.v4.txt, 19752.v5.txt,
19752.v6.txt, 19752.v7.branch-1.txt, 19752.v7.txt
>
>
> 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)

Mime
View raw message