[
https://issues.apache.org/jira/browse/HBASE-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062216#comment-13062216
]
Nicolas Spiegelberg commented on HBASE-4057:
--------------------------------------------
@Andrew : we're trying to figure out the best way to expose this data.
Perceived options:
1. Write a Java utility and expose via bin/hbase
2. Put into Ruby shell
3. HTTP-get
One of the complaints that our operations developers had was being forced to
use Ruby for scripting if they go through the shell (they are mostly Python),
so integrating that isn't a high pri for us. I was thinking the benefit of
using HTTP-get over Java util is that we don't have to design a public RPC
interface, but maybe RPC is the best solution.
> Implement HBase version of "show processlist"
> ---------------------------------------------
>
> Key: HBASE-4057
> URL: https://issues.apache.org/jira/browse/HBASE-4057
> Project: HBase
> Issue Type: New Feature
> Components: client, regionserver
> Reporter: Nicolas Spiegelberg
> Assignee: Riley Patterson
>
> One of the features that our DBAs use for MySQL analysis is "show
> processlist", which gives application-level stats about the RPC threads.
> Right now, we use jstack but that is very core-developer-centric. We need to
> create a similar tool that DBA/Ops/AppDevs can use.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
