[HBASE-16765] New SteppingRegionSplitPolicy, avoid too aggressive spread of regions for small tables. - ASF JIRA

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Critical
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 1.3.0, 1.2.5, 0.98.24, 1.1.8, 2.0.0
Component/s: None
Labels:
None

Hadoop Flags:

Incompatible change
Release Note:

Hide
Introduces a new split policy: SteppingSplitPolicy
This will use a simple step function to split a region at (by default) 2 xflushSize when no other region of the same table is seen on the region server, or max-file-size when one or more other regions of the same table is seen.

In HBase 2.0 this is going to be the default. In previous versions it can be configured.

Show
Introduces a new split policy: SteppingSplitPolicy This will use a simple step function to split a region at (by default) 2 xflushSize when no other region of the same table is seen on the region server, or max-file-size when one or more other regions of the same table is seen. In HBase 2.0 this is going to be the default. In previous versions it can be configured.

Description

We just did some experiments on some larger clusters and found that while using IncreasingToUpperBoundRegionSplitPolicy generally works well and is very convenient, it does tend to produce too many regions.

Since the logic is - by design - local, checking the number of regions of the table in question on the local server only, we end with more regions then necessary.