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

Posted to issues@hbase.apache.org by "Ankit Singhal (Jira)" <ji...@apache.org> on 2019/09/24 01:56:00 UTC

[jira] [Assigned] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs

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

Ankit Singhal reassigned HBASE-23065:
-------------------------------------

    Assignee: Ankit Singhal

> [hbtop] Top-N heavy hitter user and client drill downs
> ------------------------------------------------------
>
>                 Key: HBASE-23065
>                 URL: https://issues.apache.org/jira/browse/HBASE-23065
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Ankit Singhal
>            Priority: Major
>
> After HBASE-15519, or after an additional change on top of it that provides necessary data in ClusterStatus, add drill down top-N views of activity aggregated per user or per client IP. Only a relatively small N of the heavy hitters need be tracked assuming this will be most useful when one or a handful of users or clients is generating problematic load and hbtop is invoked to learn their identity. 
> This is a critical missing piece. After drilling down to find hot regions or tables, sometimes that is not enough, we also need to know which application or subset of clients out of many may be the source of the hot spotting load. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)