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

stack commented on HBASE-19757:
-------------------------------

Seems odd that RSGroup feature is keeping lists like this:

{code}
        412         List<TableName> specialTables =
413             new 
ArrayList<TableName>(Arrays.asList(AccessControlLists.ACL_TABLE_NAME,
414               TableName.META_TABLE_NAME, TableName.NAMESPACE_TABLE_NAME, 
RSGROUP_TABLE_NAME));
415         // if quota is enabled, add corresponding system table to special 
tables list
416         if (QuotaUtil.isQuotaEnabled(conn.getConfiguration())) {
417           specialTables.add(QuotaTableUtil.QUOTA_TABLE_NAME);
418         }
{code}

There is no comment saying what is 'special' about these tables saying what 
happens to them. I'd think their 'specialness' would be an attribute of the 
core, not of a peripheral feature like rsgroup?

> System table gets stuck after enabling region server group feature in secure 
> cluster
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-19757
>                 URL: https://issues.apache.org/jira/browse/HBASE-19757
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Critical
>             Fix For: 1.4.1, 1.5.0, 2.0.0-beta-2, 2.0.0
>
>         Attachments: 19757.v1.txt, 19757.v2.txt, 19757.v3.txt, 19757.v4.txt
>
>
> I was testing on an hbase-2 secure cluster against hadoop 3 where some tables 
> were created without region server group feature.
> After adding the RSGroupAdminEndpoint and RSGroupBasedLoadBalancer to 
> hbase-site, I restarted the whole cluster.
> After the restart, hbase:meta region got stuck in transition (forever).
> {code}
> 2018-01-10 21:20:16,696 INFO  
> [org.apache.hadoop.hbase.rsgroup.RSGroupInfoManagerImpl$RSGroupStartupWorker-ctr-e137-1514896590304-8706-01-000002.hwx.site,20000,1515619212617]
>   zookeeper.MetaTableLocator: Failed verification of hbase:meta,,1 at 
> address=ctr-e137-1514896590304-8706-01-000004.hwx.site,16020,1515618538016, 
> exception=org.apache.hadoop.    hbase.NotServingRegionException: 
> hbase:meta,,1 is not online on 
> ctr-e137-1514896590304-8706-01-000004.hwx.site,16020,1515619181453
>         at 
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:3314)
>         at 
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3291)
>         at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegion(RSRpcServices.java:1355)
>         at 
> org.apache.hadoop.hbase.regionserver.RSRpcServices.getRegionInfo(RSRpcServices.java:1667)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to