[
https://issues.apache.org/jira/browse/HBASE-16561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang updated HBASE-16561:
-----------------------------------
Description: Now there are only metrics about total queue length and active
rpc handler count. But in the RWQueueRpcExecutor, there are different queues
and handlers for read/write/scan request. I thought it is necessary to add more
metrics for RWQueueRpcExecutor. When use it in production cluster, we can
adjust the config of queues and handlers according to the metrics. (was: Now
there are only metrics about total queue length and active rpc handler count.
But for the RWQueueRpcExecutor, we can have different queues and handlers for
read/write/scan request. I thought it is necessary to add more metrics for
RWQueueRpcExecutor. When use it in production cluster, we can adjust the config
of queues and handlers according to the metrics.)
> Add metrics about read/write/scan queue length and active handler count
> -----------------------------------------------------------------------
>
> Key: HBASE-16561
> URL: https://issues.apache.org/jira/browse/HBASE-16561
> Project: HBase
> Issue Type: Improvement
> Components: IPC/RPC, metrics
> Reporter: Guanghao Zhang
> Priority: Minor
>
> Now there are only metrics about total queue length and active rpc handler
> count. But in the RWQueueRpcExecutor, there are different queues and handlers
> for read/write/scan request. I thought it is necessary to add more metrics
> for RWQueueRpcExecutor. When use it in production cluster, we can adjust the
> config of queues and handlers according to the metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
