[
https://issues.apache.org/jira/browse/HBASE-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086028#comment-13086028
]
Andrew Purtell commented on HBASE-4117:
---------------------------------------
I'm not suggesting turning down good work.
However I renew my objection to the result of adding this feature as is. We end
up with a hodgepodge of methods for gathering status information or taking
administrative action. Do I use the shell? Do I grab some JSON at some path on
the server? (And at more than one path?) Do I grep the logs? This is not good
design. Why can't this information be made retrievable via the Java admin API
via RPC (and therefore the shell can manipulate it)? Why can't we have a common
interface that lets us expose this type of information by RPC or by servlet or
by logging?
> Slow Query Log
> --------------
>
> Key: HBASE-4117
> URL: https://issues.apache.org/jira/browse/HBASE-4117
> Project: HBase
> Issue Type: New Feature
> Components: ipc
> Reporter: Riley Patterson
> Assignee: Riley Patterson
> Priority: Minor
> Labels: client, ipc
> Attachments: HBASE-4117.patch
>
>
> Produce log messages for slow queries. The RPC server will decide what is
> slow based on a configurable "warn response time" parameter. Queries
> designated as slow will then output a "response too slow" message followed by
> a fingerprint of the query, and a summary limited in size by another
> configurable parameter (to limit log spamming).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
