[
https://issues.apache.org/jira/browse/HBASE-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483466#comment-16483466
]
Chia-Ping Tsai commented on HBASE-16290:
----------------------------------------
[~allan163] Nice finding. This issue had been in 2.0. So could you file another
Jira to fix it?
> 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
> Priority: Major
> 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,
> HBASE-16290.master.006.patch, HBASE-16290.master.007.patch,
> HBASE-16290.master.008.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
(v7.6.3#76005)
