[
https://issues.apache.org/jira/browse/HBASE-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027758#comment-13027758
]
stack commented on HBASE-3836:
------------------------------
+1 looks good to me Todd. Will help.
In another world, if we were starting over, all hbase 'components' would have
state and even history; a visitor could iterate all registered components and
then dump the output to UI or to monitoring tools via JMX, etc. dependent on
how system was configured.
I can do that in my next life.
> Add facility to track currently progressing actions/workflows
> -------------------------------------------------------------
>
> Key: HBASE-3836
> URL: https://issues.apache.org/jira/browse/HBASE-3836
> Project: HBase
> Issue Type: New Feature
> Components: master, regionserver
> Affects Versions: 0.92.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.92.0
>
> Attachments: hbase-3836.txt
>
>
> A lot of troubleshooting involves answering the question "well, what is your
> server doing right now?" Today, that involves some combination of
> interpreting jstack output and/or trudging through logs. Problems with these
> methods are: (a) users may not have direct ssh access to regionserver
> machines in production environments, (b) logs are very verbose, so hard to
> separate what's still going on vs stuff that might have completed, and (c)
> interpreting jstack requires a pretty good knowledge of the codebase plus
> diving into source code.
> I'd like to add a singleton (for now) which takes care of tracking any major
> actions going on in the region server and master.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
