hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gaurav Menghani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10201) Port 'Make flush decisions per column family' to trunk
Date Thu, 30 Oct 2014 23:18:34 GMT

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

Gaurav Menghani commented on HBASE-10201:
-----------------------------------------

[~stack] From my design, in this case, 1 and 4 are flushed, but 2 and 3 are retained in the
memory. But we can only mark 1 as safe. 2, 3 and 4 will all be replayed if the server crashes.
I am not sure, if this has changed in the patch.

The Per-CF change is not running in prod right now. I didn't see any big difference deploying
it out of the box with the biggest customer where we have a lot of CFs (probably also high-lighted
by the small difference in WAF). But I can try running it internally on a shadow cluster again.
Let me know if there are some interesting metrics you want me to look at.

> Port 'Make flush decisions per column family' to trunk
> ------------------------------------------------------
>
>                 Key: HBASE-10201
>                 URL: https://issues.apache.org/jira/browse/HBASE-10201
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>            Reporter: Ted Yu
>            Assignee: zhangduo
>            Priority: Critical
>             Fix For: 2.0.0, 0.99.2
>
>         Attachments: 3149-trunk-v1.txt, HBASE-10201-0.98.patch, HBASE-10201-0.98_1.patch,
HBASE-10201-0.98_2.patch, HBASE-10201-0.99.patch, HBASE-10201.patch, HBASE-10201_1.patch,
HBASE-10201_2.patch, HBASE-10201_3.patch
>
>
> Currently the flush decision is made using the aggregate size of all column families.
When large and small column families co-exist, this causes many small flushes of the smaller
CF. We need to make per-CF flush decisions.



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

Mime
View raw message