Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-17185

Purge the seek of the next block reading HFileBlocks

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Abandoned
    • 2.0.0
    • None
    • HFile

    Description

      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.

      Attachments

        1. HBASE-17185.patch
          30 kB
          Michael Stack
        2. HBASE-17185.master.001.patch
          45 kB
          Michael Stack
        3. HBASE-17185.v2.txt
          43 kB
          Michael Stack

        Issue Links

          There are no Sub-Tasks for this issue.

          Activity

            People

              Unassigned Unassigned
              stack Michael Stack
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: