hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-641) Improve master split logging
Date Tue, 27 May 2008 20:42:59 GMT

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

stack resolved HBASE-641.

       Resolution: Fixed
    Fix Version/s: 0.1.3

Applied to branch and trunk an amendment to the 'Added ...' log message.  Added file we got
the edits from.   Regards adding a log that says who is running the split, should be possible
to figure by seeing what just proceeded this log message whether its the shutdown or scanner

Fix then was a one-line change to a log message.

> Improve master split logging
> ----------------------------
>                 Key: HBASE-641
>                 URL: https://issues.apache.org/jira/browse/HBASE-641
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.1.2
>            Reporter: stack
>             Fix For: 0.1.3, 0.2.0
> I'm looking at a log around a regionserver crash on top of hdfs errors and am having
trouble deciphering whats going on.  Would help if HLog.split said who was running the split
-- the meta scanner or the shutdown processing -- and would help if messages like "2008-05-18
20:22:28,183 DEBUG org.apache.hadoop.hbase.HLog: Applied 30001 total edits" said where (or
from which file) the edits had been applied.  It seems that there are two ongoing splits happening,
two different tables.

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

View raw message