You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2019/04/22 21:42:00 UTC

[jira] [Resolved] (HBASE-19322) System tables hbase:quota|hbase:acl will be in offline state when cluster startup first time with rsgroup feature

     [ https://issues.apache.org/jira/browse/HBASE-19322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-19322.
---------------------------
    Resolution: Implemented

Resolving. Implemented by HBASE-20566. Thanks [~gsbiju]

> System tables hbase:quota|hbase:acl will be in offline state when cluster startup first time with rsgroup feature
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-19322
>                 URL: https://issues.apache.org/jira/browse/HBASE-19322
>             Project: HBase
>          Issue Type: Bug
>          Components: rsgroup
>    Affects Versions: 2.0.0-alpha-4
>            Reporter: xinxin fan
>            Priority: Major
>
> When cluster start up first time with rsgroup feature, system tables hbase:quota and hbase:acl  will be in OFFLINE state:
> {code:java}
> hbase:quota,,1511254877213.0627adae8630c21f4456984713cdffc8. state=OFFLINE, ts=Tue Nov 21 17:03:37 CST 2017 (0s ago), server=localhost,1,1
> {code}
> It seems that the balancer doesn't know which server to assign the regions,since that  rsgroup information of the two system tables found to be null.
> I read the code and found a issue in rsgroup startup procedure : the rsgroup starts up before the creating of the two system tables(hbase:quota, hbase:acl), so rsgroupStartupWorker only adds hbase:meta and hbase:namespace into default group by following function:
> {code:java}
> specialTables = masterServices.listTableNamesByNamespace(NamespaceDescriptor.SYSTEM_NAMESPACE_NAME_STR)
> {code}
>  



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