hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-698) HLog recovery is not performed after master failure
Date Thu, 21 May 2009 17:39:45 GMT

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

stack commented on HBASE-698:
-----------------------------

HBASE-1439 is talking about ownership of commit logs being orchestrated by zk; perhaps on
startup (or on assumption of master role) master can check zk if commit logs to replay.

> 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
>            Priority: Blocker
>             Fix For: 0.20.0
>
>
> 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.


Mime
View raw message