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

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

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

     [ https://issues.apache.org/jira/browse/HBASE-25004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Viraj Jasani resolved HBASE-25004.
----------------------------------
    Fix Version/s: 2.2.7
       Resolution: Fixed

> Log RegionTooBusyException details
> ----------------------------------
>
>                 Key: HBASE-25004
>                 URL: https://issues.apache.org/jira/browse/HBASE-25004
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 1.6.0, 1.3.6
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 1.7.0, 2.4.0, 2.2.7, 2.3.2
>
>         Attachments: Screenshot 2020-09-09 at 2.32.02 PM.png
>
>
> 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)