[
https://issues.apache.org/jira/browse/HBASE-16290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178681#comment-16178681
]
Chia-Ping Tsai commented on HBASE-16290:
----------------------------------------
Consider following the Yetus' naming convention.
{code}
(JIRA).(branch name).(patch number).patch
For eg. HBASE-11625.master.001.patch, HBASE-XXXXX.branch-1.2.0005.patch, etc.
{code}
see [hbase docs|http://hbase.apache.org/book.html#submitting.patches.create]
for more details.
> 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.old,
> 0001-Changes-for-HBASE-16290-to-dump-callqueue-contents.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)
