hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3836) Add facility to track currently progressing actions/workflows
Date Tue, 03 May 2011 06:14:03 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon resolved HBASE-3836.

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Committed to trunk, thanks for taking a look, Stack. I assume we'll add more of these as we
go, and hopefully don't have to wait for our next lives to make hbase easier to operate :)

> 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

View raw message