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

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.3.0, 1.2.5, 0.98.24, 1.1.8, 2.0.0
• Hadoop Flags: Incompatible change

Release Note

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.

• Assignee: Lars Hofhansl
• Reporter: Lars Hofhansl
• Created: 04/Oct/16 19:26
• Updated: 09/Nov/17 02:49
• Resolved: 01/Nov/16 21:31

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.

Issue Links

• is related to: HBASE-12451 IncreasingToUpperBoundRegionSplitPolicy may cause unnecessary region splits in rolling update of cluster