You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2008/06/03 14:12:45 UTC

[jira] Commented: (HBASE-533) Region Historian

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

Jean-Daniel Cryans commented on HBASE-533:
------------------------------------------

Now it explains everything. Thank you stack for your help!

> Region Historian
> ----------------
>
>                 Key: HBASE-533
>                 URL: https://issues.apache.org/jira/browse/HBASE-533
>             Project: Hadoop HBase
>          Issue Type: Wish
>            Reporter: Bryan Duxbury
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>         Attachments: hbase-533-v1-fix.patch, hbase-533-v1.patch, hbase-533-v2.patch, hbase-533-v3.patch, hbase-533-v4.patch
>
>
> Whenever we try to debug region splitting, assignment, compaction, etc. issues, we always end up having to look in 1-20 different log files for cryptic names of regions and try to piece together the chain of events ourselves. This is a challenging at best effort most of the time.
> What would be very useful would be a new utility I've nicknamed the Region Historian. You give it the text name of a region, and it will track down the log messages relevant to it in the master and regionserver logs. Then, it will interleave the messages in such a way that the timestamps correctly list the order of events. The result is a log summary that accurately describes what happened to a region during it's lifetime, making it much easier to try and figure out where something went wrong.
> Other things it could do would be replace cryptic log messages with simple events like "the region was split into a and b", "the region was assigned to server x", and trace the lineage of a region backwards to its parent before it came into existence.
> I'm sure there are other things we would think up that would be useful as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.