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-14623) Implement dedicated WAL for system tables
Date Fri, 16 Oct 2015 19:27:06 GMT

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

stack commented on HBASE-14623:

bq. i think your guys are still thinking of HBASE-14190. 

Yeah. This issue is filed as a sub-task of that issue.

bq. For system table has its own WAL, we would recover system table faster (fast split, fast
replay). It would probably benefit AM on system table region assignment. At this time, the
new AM is not planned to change WAL. So I think the existence of this JIRA is good for overall
system, not specific to AM.

We can discuss, sure. Should there be a WAL per system table or one WAL for all system tables?
Should we compound all system tables so assignment is easier rather than have a small system
table per domain each with their own heavyweight assignment and a complex required ordering
of assign each with their own split to run? Should we be propagating an exception in our WAL
system? And so on. Showing up with a patch that complicates an already difficult startup without
discussion/justification other than someone suggested it is going to get some pushback.

> Implement dedicated WAL for system tables
> -----------------------------------------
>                 Key: HBASE-14623
>                 URL: https://issues.apache.org/jira/browse/HBASE-14623
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>             Fix For: 2.0.0
>         Attachments: 14623-v1.txt
> As Stephen suggested in parent JIRA, dedicating separate WAL for system tables (other
than hbase:meta) should be done in new JIRA.
> This task is to fulfill the system WAL separation.

This message was sent by Atlassian JIRA

View raw message