You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sreeram Venkatasubramanian (JIRA)" <ji...@apache.org> on 2017/09/24 05:43:00 UTC
[jira] [Issue Comment Deleted] (HBASE-16290) Dump summary of
callQueue content; can help debugging
[ https://issues.apache.org/jira/browse/HBASE-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sreeram Venkatasubramanian updated HBASE-16290:
-----------------------------------------------
Comment: was deleted
(was: Hi [~chia7712],
Thank you for your comments. As suggested, I have added a new class CallQueueInfo.java to store the queue information. I have also included tests for SimpleRpcScheduler and FifoScheduler. Kindly let me know if it looks OK now.
Old patch is renamed to 0001-Dump-call-queue-summaries.patch.old. Current patch is 0001-Changes-for-HBASE-16290.patch.
Thanks,
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: 0001-Changes-for-HBASE-16290.patch, 0001-Dump-call-queue-summaries.patch.old, DebugDump_screenshot.png, 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)