Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-15179 Cell/DBB end-to-end on the write-path
  3. HBASE-17338

Treat Cell data size under global memstore heap size only when that Cell can not be copied to MSLAB

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 2.0.0
    • regionserver
    • None
    • Reviewed

    Description

      We have only data size and heap overhead being tracked globally. Off heap memstore works with off heap backed MSLAB pool. But a cell, when added to memstore, not always getting copied to MSLAB. Append/Increment ops doing an upsert, dont use MSLAB. Also based on the Cell size, we sometimes avoid MSLAB copy. But now we track these cell data size also under the global memstore data size which indicated off heap size in case of off heap memstore. For global checks for flushes (against lower/upper watermark levels), we check this size against max off heap memstore size. We do check heap overhead against global heap memstore size (Defaults to 40% of xmx) But for such cells the data size also should be accounted under the heap overhead.

      Attachments

        1. HBASE-17338_V6.patch
          88 kB
          Anoop Sam John
        2. HBASE-17338_V5.patch
          88 kB
          Anoop Sam John
        3. HBASE-17338_V4.patch
          75 kB
          Anoop Sam John
        4. HBASE-17338_V2.patch
          73 kB
          Anoop Sam John
        5. HBASE-17338_V2.patch
          63 kB
          Anoop Sam John
        6. HBASE-17338.patch
          7 kB
          Anoop Sam John

        Issue Links

          Activity

            People

              anoop.hbase Anoop Sam John
              anoop.hbase Anoop Sam John
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: