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

Hudson commented on HBASE-10212:
--------------------------------

ABORTED: Integrated in HBase-0.94 #1292 (See 
[https://builds.apache.org/job/HBase-0.94/1292/])
HBASE-10212 New rpc metric: number of active handler. (Chao Shi) (larsh: rev 
1569122)
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/ipc/HBaseRpcMetrics.java
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java


> New rpc metric: number of active handler
> ----------------------------------------
>
>                 Key: HBASE-10212
>                 URL: https://issues.apache.org/jira/browse/HBASE-10212
>             Project: HBase
>          Issue Type: Improvement
>          Components: IPC/RPC
>            Reporter: Chao Shi
>            Assignee: Chao Shi
>             Fix For: 0.94.17
>
>         Attachments: hbase-10212.patch
>
>
> The attached patch adds a new metric: number of active handler threads. We 
> found this is a good metric to measure how busy of a server. If this number 
> is too high (compared to the total number of handlers), the server has risks 
> in getting call queue full.
> We used to monitor  # reads or # writes. However we found this often produce 
> false alerts, because a read touching HDFS will produce much high workload 
> than a block-cached read.
> The attached patch is based on our internal 0.94 branch, but I think it 
> pretty easy to port to rebase to other branches if you think it is useful.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to