hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Yuan Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-16488) Starting namespace and quota services in master startup asynchronizely
Date Thu, 08 Sep 2016 06:03:20 GMT

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

Stephen Yuan Jiang updated HBASE-16488:
    Status: Patch Available  (was: Open)

> Starting namespace and quota services in master startup asynchronizely
> ----------------------------------------------------------------------
>                 Key: HBASE-16488
>                 URL: https://issues.apache.org/jira/browse/HBASE-16488
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 1.2.2, 1.1.5, 1.0.3, 2.0.0, 1.3.0, 1.4.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Stephen Yuan Jiang
>         Attachments: HBASE-16488.v1-master.patch
> From time to time, during internal IT test and from customer, we often see master initialization
failed due to namespace table region takes long time to assign (eg. sometimes split log takes
long time or hanging; or sometimes RS is temporarily not available; sometimes due to some
unknown assignment issue).  In the past, there was some proposal to improve this situation,
eg. HBASE-13556 / HBASE-14190 (Assign system tables ahead of user region assignment) or HBASE-13557
(Special WAL handling for system tables) or  HBASE-14623 (Implement dedicated WAL for system
> This JIRA proposes another way to solve this master initialization fail issue: namespace
service is only used by a handful operations (eg. create table / namespace DDL / get namespace
API / some RS group DDL).  Only quota manager depends on it and quota management is off by
default.  Therefore, namespace service is not really needed for master to be functional. 
So we could start namespace service asynchronizely without blocking master startup.

This message was sent by Atlassian JIRA

View raw message