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

Expose BucketCache values to be configured

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4.0, 2.0.0-alpha-2, 2.0.0
    • Component/s: BucketCache
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      This patch exposes configuration for Bucketcache. These configs are very similar to those for the LRU cache, but are described below:

      "hbase.bucketcache.single.factor"; /** Single access bucket size */
      "hbase.bucketcache.multi.factor"; /** Multiple access bucket size */
      "hbase.bucketcache.memory.factor"; /** In-memory bucket size */
      "hbase.bucketcache.extrafreefactor"; /** Free this floating point factor of extra blocks when evicting. For example free the number of blocks requested * (1 + extraFreeFactor) */
      "hbase.bucketcache.acceptfactor"; /** Acceptable size of cache (no evictions if size < acceptable) */
      "hbase.bucketcache.minfactor"; /** Minimum threshold of cache (when evicting, evict until size < min) */

      Show
      This patch exposes configuration for Bucketcache. These configs are very similar to those for the LRU cache, but are described below: "hbase.bucketcache.single.factor"; /** Single access bucket size */ "hbase.bucketcache.multi.factor"; /** Multiple access bucket size */ "hbase.bucketcache.memory.factor"; /** In-memory bucket size */ "hbase.bucketcache.extrafreefactor"; /** Free this floating point factor of extra blocks when evicting. For example free the number of blocks requested * (1 + extraFreeFactor) */ "hbase.bucketcache.acceptfactor"; /** Acceptable size of cache (no evictions if size < acceptable) */ "hbase.bucketcache.minfactor"; /** Minimum threshold of cache (when evicting, evict until size < min) */

      Description

      BucketCache always uses the default values for all cache configuration. However, this doesn't work for all use cases. In particular, users want to be able to configure the percentage of the cache that is single access, multi access, and in-memory access.

        Attachments

        1. HBASE-18533.branch-1.003.patch
          20 kB
          Zach York
        2. HBASE-18533.master.003.patch
          21 kB
          Zach York
        3. HBASE-18533.branch-1.002.patch
          20 kB
          Zach York
        4. HBASE-18533.master.002.patch
          21 kB
          Zach York
        5. HBASE-18533.master.001.patch
          21 kB
          Zach York
        6. HBASE-18533.branch-1.001.patch
          20 kB
          Zach York

          Activity

            People

            • Assignee:
              zyork Zach York
              Reporter:
              zyork Zach York
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: