[
https://issues.apache.org/jira/browse/HBASE-18865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177402#comment-16177402
]
Guanghao Zhang commented on HBASE-18865:
----------------------------------------
There are same problems on our cluster. If the hbase:namespace region is not
online in a config timeout, it will abort master......
And can we introduce priority for user tables? For multi-tenant scenario, there
may have different SLA for different tables. So the high priority table should
be recover firstly. Thanks.
> Ensure system tables can have their WALs split prior to user tables
> -------------------------------------------------------------------
>
> Key: HBASE-18865
> URL: https://issues.apache.org/jira/browse/HBASE-18865
> Project: HBase
> Issue Type: New Feature
> Components: wal
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Priority: Critical
> Fix For: 2.0.0
>
>
> From a comment on HBASE-14190 and repeated on HBASE-18109 from [~yangzhe1991]:
> {quote}
> If I am not wrong, for system tables expect meta we still share logs with
> user regions, so even if we have some logic to assign system tables first, we
> still need wait log splitting done and we can not guarantee logs of system
> tables are split first. So there may be a blocking task that we should make
> multi-log feature having priority and write entries of system table in the
> highest priority logs. Thanks.
> {quote}
> This is an umbrella for working out our long term plan around how we handle
> WAL prioritization and recovery.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
