[HBASE-25004] Log RegionTooBusyException details

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.0, 1.3.6
• Fix Version/s: 3.0.0-alpha-1, 1.7.0, 2.4.0, 2.2.7, 2.3.2
• Hadoop Flags: Reviewed
• Assignee: Viraj Jasani
• Reporter: Viraj Jasani
• Created: 09/Sep/20 10:18
• Updated: 16/Sep/20 22:39
• Resolved: 16/Sep/20 10:25

Description

When we throw RegionTooBusyException, it gets wrapped in RetriesExhaustedWithDetailsException at times and the original source doing batch mutation might not be able to log region name and root cause that comes with RegionTooBusyException as it is wrapped with outer RetriesExhaustedWithDetailsException and outer Exception has it's own way of logging only necessary info, which is quite acceptable. Attaching a sample screenshot.

We should at least log details of RegionTooBusyException at server side before we throw it.

Issue Links

• links to: GitHub Pull Request #2371