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

["Toshihiro Suzuki (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997391#comment-16997391 ] 

Toshihiro Suzuki edited comment on HBASE-23065 at 12/16/19 3:41 PM:
--------------------------------------------------------------------

Pushed to master.

Trying to push to branch-2. It looks like we need some changes for this branch.


was (Author: brfrn169):
Pushed to master.

Trying to push to branch-2. It looks like we need some changes for this branch.

 

> [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
>          Components: hbtop, Operability
>            Reporter: Andrew Kyle Purtell
>            Assignee: Ankit Singhal
>            Priority: Major
>             Fix For: 3.0.0
>
>
> 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)