[
https://issues.apache.org/jira/browse/HBASE-17627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15866682#comment-15866682
]
Ashu Pachauri commented on HBASE-17627:
---------------------------------------
[~ghelmling] The test failures seem unrelated. I checked the test case, it
waits for thrift server to start for 10 seconds and then gives up; this may be
a flaky test case. Also, it succeeded several times locally for me.
bq. They way we currently expose number of active handlers, here and in the
RpcServer, is a bit flawed. Since it is a point in time metric, it can miss
spikes in activity which clear before the metrics collection happen. Ultimately
it might be better to report something like "number of handler milliseconds
consumed" (millis duration for each call, summed up), but that is really a
separate discussion.
Agreed. Thrift servers expose per call type processing time histograms
(putMultiple, getScannerRows etc) which may be indicative of how busy thrift
workers are, though it's often skewed by a small percentage of slow calls going
to only a fraction of workers.
> Active workers metric for thrift
> --------------------------------
>
> Key: HBASE-17627
> URL: https://issues.apache.org/jira/browse/HBASE-17627
> Project: HBase
> Issue Type: Improvement
> Components: Thrift
> Reporter: Ashu Pachauri
> Assignee: Ashu Pachauri
> Attachments: HBASE-17627.master.001.patch
>
>
> It would be good to have a metric for number of active handlers on thrift
> servers, which gives a good indication of business of a thrift server.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
