[
https://issues.apache.org/jira/browse/HBASE-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206949#comment-16206949
]
Sreeram Venkatasubramanian commented on HBASE-16290:
----------------------------------------------------
Hi [~chia7712], I have implemented the suggested change for FifoRpcScheduler.
FifoRpcScheduler uses ThreadPoolExecutor. Unlike SimpleRpcScheduler, there
seems to be no easy way to unit test the number of tasks inside
ThreadPoolExecutor. Minimum of 1 worker task always runs in ThreadPoolExecutor
and it consumes some tasks from the work queue. So the input number of tasks
does not end up matching with the tasks held by ThreadPoolExecutor (which is
lesser in number). Any suggestions on this ?
> Dump summary of callQueue content; can help debugging
> -----------------------------------------------------
>
> Key: HBASE-16290
> URL: https://issues.apache.org/jira/browse/HBASE-16290
> Project: HBase
> Issue Type: Bug
> Components: Operability
> Affects Versions: 2.0.0
> Reporter: stack
> Assignee: Sreeram Venkatasubramanian
> Labels: beginner
> Fix For: 2.0.0
>
> Attachments: DebugDump_screenshot.png, HBASE-16290.master.001.patch,
> HBASE-16290.master.002.patch, HBASE-16290.master.003.patch,
> HBASE-16290.master.004.patch, HBASE-16290.master.005.patch, Sample Summary.txt
>
>
> Being able to get a clue what is in a backedup callQueue could give insight
> on what is going on on a jacked server. Just needs to summarize count, sizes,
> call types. Useful debugging. In a servlet?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
