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

Port HFileBlockIndex improvement from HBASE-5987

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.94.3, 0.95.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Excerpt from HBASE-5987:
      First, we propose to lookahead for one more block index so that the HFileScanner would know the start key value of next data block. So if the target key value for the scan(reSeekTo) is "smaller" than that start kv of next data block, it means the target key value has a very high possibility in the current data block (if not in current data block, then the start kv of next data block should be returned. Indexing on the start key has some defects here) and it shall NOT query the HFileBlockIndex in this case. On the contrary, if the target key value is "bigger", then it shall query the HFileBlockIndex. This improvement shall help to reduce the hotness of HFileBlockIndex and avoid some unnecessary IdLock Contention or Index Block Cache lookup.

      This JIRA is to port the fix to HBase trunk, etc.

        Attachments

        1. 6032.094.txt
          34 kB
          Michael Stack
        2. 6032-ports-5987.txt
          32 kB
          Ted Yu
        3. 6032-ports-5987-v2.txt
          32 kB
          Ted Yu
        4. 6032v3.txt
          34 kB
          Michael Stack

          Issue Links

            Activity

              People

              • Assignee:
                zhihyu@ebaysf.com Ted Yu
                Reporter:
                zhihyu@ebaysf.com Ted Yu
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: