You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/28 21:37:58 UTC

[jira] [Created] (HBASE-17185) Purge the seek of the next block reading HFileBlocks

stack created HBASE-17185:
-----------------------------

             Summary: Purge the seek of the next block reading HFileBlocks
                 Key: HBASE-17185
                 URL: https://issues.apache.org/jira/browse/HBASE-17185
             Project: HBase
          Issue Type: Improvement
          Components: HFile
    Affects Versions: 2.0.0
            Reporter: stack
            Assignee: stack


When we read HFileBlocks, we read the asked-for block AND the next block's header which we add to a cache (see HBASE-17072). We do this extra read to get the next block's length purportedly. This seek of the next block's header complicates the HFileBlock construction (not to mind other consequences -- again see HBASE-17072).

Study done in HBASE-17072 shows that we normally do not need this extra read of the next block's header. In the usual case, the length of the block is gotten from the hfile index.

A simplification of block reading can be done purging this extra header read. We can also save some space in cache.



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