[HBASE-15324] Jitter may cause desiredMaxFileSize overflow in ConstantSizeRegionSplitPolicy and trigger unexpected split

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.3, 2.0.0
• Fix Version/s: 1.3.0, 1.2.5, 1.1.8, 2.0.0
• Hadoop Flags: Reviewed
• Assignee: Yu Li
• Reporter: Yu Li
• Created: 25/Feb/16 06:17
• Updated: 09/Nov/17 00:24
• Resolved: 30/Mar/16 20:36

Description

We introduce jitter for region split decision in HBASE-13412, but the following line in ConstantSizeRegionSplitPolicy may cause long value overflow if MAX_FILESIZE is specified to Long.MAX_VALUE:

this.desiredMaxFileSize += (long)(desiredMaxFileSize * (RANDOM.nextFloat() - 0.5D) * jitter);

In our case we specify MAX_FILESIZE to Long.MAX_VALUE to prevent target region to split.

Issue Links

• is related to: HBASE-17058 Lower epsilon used for jitter verification from HBASE-15324