[
https://issues.apache.org/jira/browse/HBASE-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187700#comment-16187700
]
Sreeram Venkatasubramanian commented on HBASE-16290:
----------------------------------------------------
Hi [~chia7712],
{quote}Can we have FifoRpcScheduler provide the more information of holding
CallRunner? What about wrapping the CallRunner as Runnable + getCallRunner()?
We can call ThreadPoolExecutor#getQueue to list the holding {{Runnable +
getCallRunner()}.{quote}
I tried above suggestion and have run into an issue. The submit() method of
ThreadPoolExecutor creates a FutureTask using the CallRunner and stores the
FutureTask in the workQueue (which is returned by getQueue). But the FutureTask
does not expose CallRunner callable directly - it is a private member.
Any thoughts on this ? Or should I submit the current patch to the review board.
Kindly advise.
Regards,
Sreeram
> 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)
