Viraj Jasani created HBASE-25004:
------------------------------------
Summary: Log RegionTooBusyException details
Key: HBASE-25004
URL: https://issues.apache.org/jira/browse/HBASE-25004
Project: HBase
Issue Type: Task
Reporter: Viraj Jasani
Assignee: Viraj Jasani
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
