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

Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2021/11/24 22:36:00 UTC

[jira] [Reopened] (HBASE-26479) Print too slow/big scan's operation_id in region server log

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

Andrew Kyle Purtell reopened HBASE-26479:
-----------------------------------------

The commit to branch-2 breaks compilation. (branch-2 has HBaseTestingUtility, not HBaseTestingUtil). Reverted commit from branch-2.

> Print too slow/big scan's operation_id in region server log
> -----------------------------------------------------------
>
>                 Key: HBASE-26479
>                 URL: https://issues.apache.org/jira/browse/HBASE-26479
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver, scan
>            Reporter: Xuesen Liang
>            Assignee: Xuesen Liang
>            Priority: Minor
>             Fix For: 2.5.0, 3.0.0-alpha-2
>
>         Attachments: HBASE-26479.patch
>
>
> Tracing is very important in large-scale distributed systems.
> The attribute *__operation.attributes.id_*  of a scan request can be used as trace id between hbase client and region server.
> We should print operation id in region server's log if the scan request is too slow or too big.
> It will be very helpful for finding problematic requests.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)