[
https://issues.apache.org/jira/browse/HBASE-11062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979270#comment-13979270
]
stack commented on HBASE-11062:
-------------------------------
Suggest we do Andy's later suggestion, do this as a screen in external app or
in master first and then figure how to get it working in a terminal console?
(links/lynx?)
A basis could be the federation of jmx metrics, or better, a rolling window of
jmx readings (1m, 5m, 15m). Or we'd keep metrics in a table for tools like
this to read; this would probably be the better way to go.
JMX was supposed to have a federated bean view which would have been nice here
but seems stalled, jmx 2.0 is stalled... so maybe trying to get a view on
cluster via jmx is non-starter and we should go another route.. jmx emissions
are fine for a tcollector and its ilk but for an aggregated view in master or
in an htop console, it seems like a bunch of custom work -- and jmx w/ its
reliance on rmi is probably just a no-go.
> htop
> ----
>
> Key: HBASE-11062
> URL: https://issues.apache.org/jira/browse/HBASE-11062
> Project: HBase
> Issue Type: New Feature
> Reporter: Andrew Purtell
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
