hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5186) Add metrics to ThriftServer
Date Wed, 01 Feb 2012 12:45:06 GMT

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

Phabricator commented on HBASE-5186:

sc has commented on the revision "HBASE-5186 [jira] Add metrics to ThriftServer".

  src/main/java/org/apache/hadoop/hbase/thrift/CallQueue.java:126 @tedyu: On second thought,
I think using draintTo() might still be better.

  Iterating underlyingQueue and then calling clear() doesn't work for the case that maxElements
is given. Also there may be some thread-safe issues need to be solved.

  Am I understanding your comment correctly? What do you think?


> Add metrics to ThriftServer
> ---------------------------
>                 Key: HBASE-5186
>                 URL: https://issues.apache.org/jira/browse/HBASE-5186
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>         Attachments: HBASE-5186.D1461.1.patch, HBASE-5186.D1461.2.patch, HBASE-5186.D1461.3.patch,
HBASE-5186.D1461.4.patch, HBASE-5186.D1461.5.patch, HBASE-5186.D1461.6.patch, HBASE-5186.D1461.7.patch
> It will be useful to have some metrics (queue length, waiting time, processing time ...)
similar to Hadoop RPC server. This allows us to monitor system health also provide a tool
to diagnose the problem where thrift calls are slow.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message