You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Zheng Wang (Jira)" <ji...@apache.org> on 2020/07/01 02:39:00 UTC

[jira] [Created] (HBASE-24664) Some changing of split region by overall region size rather than only one store size

Zheng Wang created HBASE-24664:
----------------------------------

             Summary: Some changing of split region by overall region size rather than only one store size
                 Key: HBASE-24664
                 URL: https://issues.apache.org/jira/browse/HBASE-24664
             Project: HBase
          Issue Type: Improvement
          Components: regionserver
            Reporter: Zheng Wang
            Assignee: Zheng Wang


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)


HBASE-24530 introduced a new SteppingAllStoresSizeSplitPolicy, and as discussed in its comments and related [thread|[https://lists.apache.org/thread.html/r08a8103e2532eb667a0fcb4efa8a4117b3f82e6251bc4bd0bc157c26%40%3Cdev.hbase.apache.org%3E]],
we should do follow-on tasks in this new issue.
1. Set SteppingAllStoresSizeSplitPolicy as default
2. Mark SteppingSplitPolicy and IncreasingToUpperBoundRegionSplitPolicy.java as deprecated
3. Fix ConstantSizeRegionSplitPolicy to split region by overall region size also



--
This message was sent by Atlassian Jira
(v8.3.4#803005)