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

Some changing of split region by overall region size rather than only one store size

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0-alpha-1, 2.4.0
    • Fix Version/s: 3.0.0-alpha-1, 2.4.0
    • Component/s: regionserver
    • Labels:
      None

      Description

      As a distributed cluster, HBase distribute loads in unit of region, so if region grows too big,
      it will bring some negative effects, such as:
      1. Harder to homogenize disk usage(consider locality)
      2. Might cost more time on region opening
      3. After split, the daughter region might lead to more io cost on compaction in a short time(if write evenly)

      I tried to introduce a new SteppingAllStoresSizeSplitPolicy in HBASE-24530, but after discussed in comments and related thread, finally we decide to change the existing split policy with a new option that if it should count all store files, and for master it would be true, else false.

        Attachments

          Activity

            People

            • Assignee:
              filtertip Zheng Wang
              Reporter:
              filtertip Zheng Wang
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: