[jira] [Commented] (HBASE-11062) hbtop

["Michael Stack (Jira)" <ji...@apache.org>]

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

Michael Stack commented on HBASE-11062:
---------------------------------------

[~brfrn169] just some comments on this utility after using it some.
 * First, it is very nice. Thanks.
 * I was looking at why so many hits to hbase:meta and using the 'region' mode I could see that actually the hits to meta were generally low; it was just on occasion that hbase:meta was hit hard. In the UI, the server carrying meta can have high hits because of meta+neighbors and it is easy to accredit them all to meta when it is not always the case. This by-Region view helps.
 * I switched to Client mode and I could see the request by client and what was interesting was that the hits to meta came from CM or the Master node doing their Scans but when these were happening the hits on meta spiked up. Obvious I suppose but w/o knowing where the Scans were coming from, its easy to think clients are running wild doing too many meta lookups.
 * It looks like this 'client' mode could help identify 'bad actors' since it uses src host ip rather than 'user' which is pretty useless if all clients identify w/ same 'user' name.

What is an FREAD/S? What is SF and #SF?

Thanks.

> hbtop
> -----
>
>                 Key: HBASE-11062
>                 URL: https://issues.apache.org/jira/browse/HBASE-11062
>             Project: HBase
>          Issue Type: New Feature
>          Components: hbtop
>            Reporter: Andrew Kyle Purtell
>            Assignee: Toshihiro Suzuki
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.0, 2.1.7, 2.2.2
>
>         Attachments: HBASE-11062-master-addendum-v1.patch
>
>
> A top-like monitor could be useful for testing, debugging, operations of clusters of moderate size, and possibly for diagnosing issues in large clusters.
> Consider a curses interface like the one presented by atop (http://www.atoptool.nl/images/screenshots/genericw.png) - with aggregate metrics collected over a monitoring interval in the upper portion of the pane, and a listing of discrete measurements sorted and filtered by various criteria in the bottom part of the pane. One might imagine a cluster overview with cluster aggregate metrics above and a list of regionservers sorted by utilization below; and a regionserver view with process metrics above and a list of metrics by operation type below, or a list of client connections, or a list of threads, sorted by utilization, throughput, or latency. 
> Generically 'htop' is taken but would be distinctive in the HBase context, a utility org.apache.hadoop.hbase.HTop
> No need necessarily for a curses interface. Could be an external monitor with a web front end as has been discussed before. I do like the idea of a process that runs in a terminal because I interact with dev and test HBase clusters exclusively by SSH. 
> UPDATE:
> The tool name is changed from htop to hbtop.



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