[HBASE-24465] Normalizer should consider region max file size when planning merges

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Component/s: master, Normalizer
• Assignee: Unassigned
• Reporter: Nick Dimiduk
• Created: 28/May/20 23:20
• Updated: 09/Oct/20 17:17
• Resolved: 09/Oct/20 17:17

Description

When the normalizer plans its actions, it does not consider hbase.hregion.max.filesize. This means it could get into a merge/split loop in collaboration with the region server: the normalizer sees two regions are smaller than the table average, it merges them. The resulting region is larger that this max file size, so the region server splits them. Repeat.