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

Jean-Daniel Cryans updated HBASE-698:
-------------------------------------

    Attachment: hbase-698.patch

This patch fixes the original issue (or as much we can do without appends). 
This happens on a master failover:

{code}
2009-07-07 14:45:28,097 INFO org.apache.hadoop.hbase.master.HMaster: Found log 
folder : jdcryans.local,60020,1246991630883
2009-07-07 14:45:28,097 INFO org.apache.hadoop.hbase.master.HMaster: Log folder 
belongs to an existing region server
{code}

Whn know about the alive RS since we just scanned the rs folder in ZK. Then if 
I kill -9 both Master and RS then I restart the cluster I see:
{code}
2009-07-07 14:47:10,034 DEBUG org.apache.hadoop.hbase.master.HMaster: This is a 
fresh start, proceeding with normal startup
2009-07-07 14:47:10,038 INFO org.apache.hadoop.hbase.master.HMaster: Found log 
folder : jdcryans.local,60020,1246991630883
2009-07-07 14:47:10,038 INFO org.apache.hadoop.hbase.master.HMaster: Log folder 
doesn't belong to a known region server, splitting
2009-07-07 14:47:10,043 INFO org.apache.hadoop.hbase.regionserver.HLog: 
Splitting 1 hlog(s) in 
hdfs://localhost:9000/hbase/.logs/jdcryans.local,60020,1246991630883
...
{code}

I also removed the log splitting stuff in BaseScanner.

> 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
>            Reporter: Clint Morgan
>            Assignee: Jean-Daniel Cryans
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: 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.

Reply via email to