You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2020/09/09 10:19:00 UTC

[jira] [Created] (HBASE-25004) Log RegionTooBusyException details

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)