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-12405) WAL accounting by Store
Date Sat, 07 Mar 2015 01:31:39 GMT

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

stack commented on HBASE-12405:
-------------------------------

So, I'll commit in a day or so.

[~Apache9] So, I want to do a ITBLL that exercises this new functionality. We talked about
what it would look like,  of how I'd have to write 3 columns; one small, one medium, and then
a large one.  I suppose the ITBLL column could be the middle-sized one?  The aim is that by
hbase-1.1, this is on and as tested as anything is around these parts.

> WAL accounting by Store
> -----------------------
>
>                 Key: HBASE-12405
>                 URL: https://issues.apache.org/jira/browse/HBASE-12405
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>    Affects Versions: 2.0.0, 1.1.0
>            Reporter: zhangduo
>            Assignee: zhangduo
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-12405.patch, HBASE-12405_1.patch, HBASE-12405_2.patch, HBASE-12405_3.patch,
HBASE-12405_4.patch
>
>
> HBASE-10201 has made flush decisions per Store, but has not done enough work on HLog,
so there are two problems:
> 1. We record minSeqId both in HRegion and FSHLog, which is a duplication.
> 2. There maybe holes in WAL accounting.
>     For example, assume family A with sequence id 1 and 3, family B with seqId 2. If
we flush family A, we can only record that WAL before sequence id 1 can be removed safely.
If we do a replay at this point, sequence id 3 will also be replayed which is unnecessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message