[jira] [Commented] (HBASE-11062) hbtop
[ https://issues.apache.org/jira/browse/HBASE-11062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911569#comment-16911569 ] Krishna Maheshwari commented on HBASE-11062: This is very nice Toshi. Is it possible to add clients in addition to Region/Namespace/Table/RegionServer? That would help some admins identify which clients are driving load on their HBase so that they can better implement quotas, etc. > hbtop > - > > Key: HBASE-11062 > URL: https://issues.apache.org/jira/browse/HBASE-11062 > Project: HBase > Issue Type: New Feature > Components: hbtop >Reporter: Andrew Purtell >Assignee: Toshihiro Suzuki >Priority: Major > > 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.2#803003)
[jira] [Resolved] (HBASE-22498) Misleading statement in document
[ https://issues.apache.org/jira/browse/HBASE-22498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna Maheshwari resolved HBASE-22498. Resolution: Invalid Release Note: Wrong project > Misleading statement in document > > > Key: HBASE-22498 > URL: https://issues.apache.org/jira/browse/HBASE-22498 > Project: HBase > Issue Type: Bug > Components: phoenix >Affects Versions: 2.1.4 >Reporter: Krishna Maheshwari >Priority: Minor > > [https://svn.apache.org/repos/asf/phoenix/site/source/src/site/markdown/views.md] > has the following misleading statement as HBase scaling is not limited by > number of tables but rather number of overall regions. > "The standard SQL view syntax (with some limitations) is now supported by > Phoenix to enable multiple virtual tables to all share the same underlying > physical HBase table. This is especially important in HBase, as you cannot > realistically expect to have more than perhaps up to a hundred physical > tables and continue to get reasonable performance from HBase." > This should be revised to state: > "The standard SQL view syntax (with some limitations) is now supported by > Phoenix to enable multiple virtual tables to all share the same underlying > physical HBase table." > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-22498) Misleading statement in document
Krishna Maheshwari created HBASE-22498: -- Summary: Misleading statement in document Key: HBASE-22498 URL: https://issues.apache.org/jira/browse/HBASE-22498 Project: HBase Issue Type: Bug Components: phoenix Affects Versions: 2.1.4 Reporter: Krishna Maheshwari [https://svn.apache.org/repos/asf/phoenix/site/source/src/site/markdown/views.md] has the following misleading statement as HBase scaling is not limited by number of tables but rather number of overall regions. "The standard SQL view syntax (with some limitations) is now supported by Phoenix to enable multiple virtual tables to all share the same underlying physical HBase table. This is especially important in HBase, as you cannot realistically expect to have more than perhaps up to a hundred physical tables and continue to get reasonable performance from HBase." This should be revised to state: "The standard SQL view syntax (with some limitations) is now supported by Phoenix to enable multiple virtual tables to all share the same underlying physical HBase table." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
