[HBASE-16488] Starting namespace and quota services in master startup asynchronously - ASF JIRA

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Resolved
Priority: Major
Resolution: Won't Fix
Affects Version/s: 1.3.0, 1.0.3, 1.4.0, 1.1.5, 1.2.2, 2.0.0
Fix Version/s: None
Component/s: master
Labels:
None

Hadoop Flags:

Reviewed
Release Note:

Hide
Provide an option to start namespace service in asynchronized manner without blocking master startup. This can avoid 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).

Show
Provide an option to start namespace service in asynchronized manner without blocking master startup. This can avoid 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).

Description

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 tables).

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.