hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1823) Ability for Scanners to bypass the block cache
Date Fri, 11 Sep 2009 22:03:57 GMT

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

stack commented on HBASE-1823:

After back and forth jgray on irc, seems like he had wrong jar in way.

I reviewed patch. +1 on commit.

> Ability for Scanners to bypass the block cache
> ----------------------------------------------
>                 Key: HBASE-1823
>                 URL: https://issues.apache.org/jira/browse/HBASE-1823
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: client, regionserver
>    Affects Versions: 0.20.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>             Fix For: 0.20.1, 0.21.0
>         Attachments: HBASE-1823-v1.patch, HBASE-1823-v2.patch, HBASE-1823-v3.patch, HBASE-1823-v4.patch
> There are a number of use cases where exposing the ability to not cache blocks during
a scan would be valuable.  For example, running row counts.
> The LRU is scan-resistant, so it does provide some protection already, but even in that
case all you prevent is the eviction of hot blocks.  The LRU still runs many evictions and
the blocks are referenced for much longer periods of time, so this adds enormous stress to
the GC.
> Compactions already do this.  This issue is about exposing that as a switch to the client-side
Scan object (will also enable it for MR jobs then).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message