hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-4434) seek optimization: don't do eager HFile Scanner next() unless the next KV is needed
Date Fri, 23 Sep 2011 20:07:28 GMT

     [ https://issues.apache.org/jira/browse/HBASE-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-4434.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.92.0
     Hadoop Flags: [Reviewed]

Committed to 0.92 branch and to TRUNK.  Thanks for the sweet patch Kannan.

> seek optimization: don't do eager HFile Scanner next() unless the next KV is needed
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-4434
>                 URL: https://issues.apache.org/jira/browse/HBASE-4434
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Kannan Muthukkaruppan
>            Assignee: Kannan Muthukkaruppan
>             Fix For: 0.92.0
>
>         Attachments: HBASE-4434.txt
>
>
> When a seek/reseek is done on StoreFileScanner, in addition to setting the current KV,
it also does a HFileScanner level next() ahead of time even if the next KV is never actually
required. This inefficiency can potentially result in additional disk seeks and sub-optimal
use of the block cache (primarily for cases where the KVs are large and each occupies an HFile
block of its own).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message