HBase
  1. HBase
  2. HBASE-11581

Add option so CombinedBlockCache L2 can be null (fscache)

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BlockCache
    • Labels:

      Description

      Add option, mostly for comparison's sake, that allows a deploy orchestrated by CombinedBlockCache such that its L1 is LruBlockCache for META blocks but DATA blocks are fetched each time (we don't try and cache them, no blockcache churn).

      In operation, i can see fscache coming around to cover the fetched DATA blocks such that if the DATA blocks fit in fscache, seeks go to zero.

      This setup for sure runs slower. Will publish numbers elsewhere. Meantime, here is a patch to enable this option.

        Activity

        stack created issue -
        stack made changes -
        Field Original Value New Value
        Attachment 11581.txt [ 12657497 ]
        stack made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Assignee stack [ stack ]
        stack made changes -
        Labels beginner beginners
        stack made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Release Note Add hbase.combinedblockcache.l2.null configuration. When set to true, BlockCache uses CombinedBlockCache where L1 is instance of LruBlockCache carrying META blocks and L2 is null: i.e. DATA blocks are fetched each time.
        Resolution Invalid [ 6 ]
        Sean Busbey made changes -
        Labels beginner beginners beginner

          People

          • Assignee:
            stack
            Reporter:
            stack
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development