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

Make BlockCache eviction thresholds configurable

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 0.94.0
    • 0.95.0
    • io
    • None
    • Reviewed
    • Hide
      From now on, the block cache will use all the memory it's given as its upper bound was raised from 85% to 99%. The lower bound for evictions, called "minimum factor", was raised from 75% to 95% and is now configurable via "hbase.lru.blockcache.min.factor". This means that 4% of the block cache is evicted at a time instead of 10%, so evictions may run more often but each will be less disruptive.
      Show
      From now on, the block cache will use all the memory it's given as its upper bound was raised from 85% to 99%. The lower bound for evictions, called "minimum factor", was raised from 75% to 95% and is now configurable via "hbase.lru.blockcache.min.factor". This means that 4% of the block cache is evicted at a time instead of 10%, so evictions may run more often but each will be less disruptive.

    Description

      Some of our customers found that tuning the BlockCache eviction thresholds made test results different in their test environment. However, those thresholds are not configurable in the current implementation. The only way to change those values is to re-compile the HBase source code. We wonder if it is possible to make them configurable.

      Attachments

        1. hbase-6312_v3.patch
          4 kB
          Jie Huang
        2. hbase-6312_v2.patch
          3 kB
          Jie Huang
        3. hbase-6312.patch
          4 kB
          Jie Huang

        Issue Links

          Activity

            People

              grace.huang Jie Huang
              grace.huang Jie Huang
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: