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

Old hbase.regionserver.global.memstore.upperLimit and lowerLimit properties are ignored if present

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0.1, 1.1.0, 2.0.0
    • Fix Version/s: 1.0.2, 1.2.0, 1.1.1, 2.0.0
    • Component/s: regionserver
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      If hbase.regionserver.global.memstore.upperLimit or lowerLimit are present we should use them instead of hbase.regionserver.global.memstore.size or hbase.regionserver.global.memstore.size.lower.limit respectively. The current implementation of HeapMemorySizeUtil.getGlobalMemStorePercent() and getGlobalMemStoreLowerMark() asumes that if the new properties are not defined then we should use the old configurations, however the new properties are defined in hbase-default.xml which makes the old configuration names useless and this has a direct impact when doing a rolling upgrade and hbase-site.xml hasn't been changed to handle the new property names exclusively.

        Attachments

        1. HBASE-13729.4.patch
          2 kB
          Esteban Gutierrez
        2. HBASE-13729.3.patch
          2 kB
          Esteban Gutierrez
        3. HBASE-13729.2.patch
          2 kB
          Esteban Gutierrez
        4. 0001-HBASE-13729-Old-hbase.regionserver.global.memstore.u.patch
          1 kB
          Esteban Gutierrez

          Activity

            People

            • Assignee:
              esteban Esteban Gutierrez
              Reporter:
              esteban Esteban Gutierrez
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: