[HBASE-25835] Ignore duplicate split requests from regionserver reports

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.3
• Fix Version/s: 3.0.0-alpha-1, 2.5.0, 2.4.3
• Hadoop Flags: Reviewed
• Assignee: Andrew Kyle Purtell
• Reporter: Andrew Kyle Purtell
• Created: 02/May/21 20:52
• Updated: 06/May/21 02:25
• Resolved: 04/May/21 17:05

Description

A SplitTableRegionProcedure may already be running when a regionserver report is received that includes a split request. The outcome is multiple SplitTableRegionProcedure procedures scheduled for the split request, only one of which can succeed. The others error out. Perhaps it is only WARN level noise in the logs that will cause operator concern, but is clearly not correct.

Do not create a split procedure in response to a region state change report if the region is not open or already splitting.

Issue Links

• links to: GitHub Pull Request #3218