You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/03/01 20:52:00 UTC
[jira] [Updated] (HBASE-18865) Ensure system tables can have their
WALs split prior to user tables
[ https://issues.apache.org/jira/browse/HBASE-18865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-18865:
--------------------------
Fix Version/s: (was: 2.0.0)
> 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
>
> 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
(v7.6.3#76005)