[ https://issues.apache.org/jira/browse/HBASE-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13999363#comment-13999363 ]
Hudson commented on HBASE-10212: -------------------------------- ABORTED: Integrated in HBase-TRUNK #5132 (See [https://builds.apache.org/job/HBase-TRUNK/5132/]) Amend HBASE-10561 Forward port: HBASE-10212 New rpc metric: number of active handler (liangxie: rev 1594126) * /hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/ipc/MetricsHBaseServerSource.java * /hbase/trunk/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/ipc/MetricsHBaseServerSourceImpl.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/MetricsHBaseServerWrapperStub.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestRpcMetrics.java HBASE-10561 Forward port: HBASE-10212 New rpc metric: number of active handler (liangxie: rev 1594117) * /hbase/trunk/hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/ipc/MetricsHBaseServerWrapper.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/FifoRpcScheduler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/MetricsHBaseServerWrapperImpl.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcScheduler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/MetricsHBaseServerWrapperStub.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.2#6252)