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] [Commented] (HBASE-3836) Add facility to track currently progressing actions/workflows
Date Sat, 30 Apr 2011 23:13:03 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027402#comment-13027402

Todd Lipcon commented on HBASE-3836:

Overview of the design:

Add a TaskMonitor class which serves as the central place to track ongoing actions. It has:
-- MonitoredTask createTask("Description")
-- List<MonitoredTask> getRecentTasks()

The MonitoredTask interface has methods to update a status string and mark the task as complete
or aborted.

We can use tricky WeakReference magic to make sure that, if the MonitoredTask is leaked by
the user who called createTask, it will be automatically marked as aborted.

The TaskMonitor will automatically purge any tasks that have been leaked, and also purge completed/aborted
tasks after some period of elapsed time.

The idea is that the TaskMonitor will be exposed through the web consoles, so users can easily
understand what's going on.

> 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
> 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