[
https://issues.apache.org/jira/browse/HBASE-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730935#action_12730935
]
Jean-Daniel Cryans commented on HBASE-698:
------------------------------------------
Ah well I tested it and it's all OK because of the sequence ID. I used current
0.19, created a table, inserted 500 rows, then killed -9. I redid the same
thing in the second run but with a different column family name and shut down
clean. I then applied the patch, restarted and I saw:
{code}
2009-07-14 12:06:05,783 DEBUG org.apache.hadoop.hbase.regionserver.HRegion:
Opening region .META.,,1/1028785192
2009-07-14 12:06:05,789 DEBUG org.apache.hadoop.hbase.regionserver.HStore:
loaded
/tmp/hbase-jdcryans/hbase/.META./1028785192/info/info/7874001023615296020,
isReference=false, sequence id=512, length=559, majorCompaction=false
2009-07-14 12:06:05,789 DEBUG org.apache.hadoop.hbase.regionserver.HStore:
Loaded 1 file(s) in hstore 1028785192/info, max sequence id 512
2009-07-14 12:06:05,791 DEBUG org.apache.hadoop.hbase.regionserver.HStore:
Applied 0, skipped 7 because sequence id <= 512
{code}
So basically it's ok.
> HLog recovery is not performed after master failure
> ---------------------------------------------------
>
> Key: HBASE-698
> URL: https://issues.apache.org/jira/browse/HBASE-698
> Project: Hadoop HBase
> Issue Type: Bug
> Components: master, regionserver
> Affects Versions: 0.1.2, 0.2.1, 0.19.3
> Reporter: Clint Morgan
> Assignee: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.20.0, 0.19.4
>
> Attachments: hbase-698-0.19.patch, hbase-698.patch
>
>
> I have a local cluster running, and its logging to
> <hbase>/log_X.X.X.X_1213228101021_60020/
> Then I kill both master and regionserver, and restart. Looking through
> the logs I don't see anything about trying to recover from this hlog,
> it just creates a new hlog alongside the existing one (with a new
> startcode). The older hlog seems to be ignored, and the tables
> created in the inital session are all gone.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
