hbase-issues mailing list archives

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

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

stack commented on HBASE-18109:

[~whitesky] Of course but please talk out loud in here in this issue so we can help out if

[~yangzhe1991] Nod. We should make AM respect priorities. Seems easy enough. On log splitting,
yeah, all goes into the one bucket (log splitting needs to move to pv2 too but that is another
issue). Even so, priority should help since assign can't start till log split is done.

Hopefully w/ the async dfsclient in place, running with multiple WALs will involve less friction.
We'll have to plumb in priority splitting logs as you suggest Phil. 

> 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