hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18109) Assign system tables first (priority)
Date Fri, 02 Jun 2017 09:12:04 GMT

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

Phil Yang commented on HBASE-18109:

We also have a scenario for assigning some tables first. But not system table. Some of our
services have two kinds of tables in HBase, meta tables and data tables. If some meta tables
regions is not online, the services can not work for some queries even if all data table regions
are online. So to reduce MTTR for the service when HBase cluster down. We have to use two
HBase clusters to save two kinds of tables so the meta table MTTR will be much lower.

If we want to have priority in assignment, I think the most important part is not in AM, it
is log split and replay. Now all table will in same log file so we can not replay some tables
first. We can assign hbase:meta first because the log of meta is in a independent log file.
So we may need multi-log feature to write different priority table into different logs and
they have different file names so we  can split  them in a suitable order.


> Assign system tables first (priority)
> -------------------------------------
>                 Key: HBASE-18109
>                 URL: https://issues.apache.org/jira/browse/HBASE-18109
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Region Assignment
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Priority: Critical
>             Fix For: 2.0.0
> Need this for stuff like the RSGroup table, etc. Assign these ahead of user-space regions.
> From 'Handle sys table assignment first (e.g. acl, namespace, rsgroup); currently only
hbase:meta is first.' of https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.oefcyphs0v0x

This message was sent by Atlassian JIRA

View raw message