[
https://issues.apache.org/jira/browse/HBASE-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619082#action_12619082
]
Jim Kellerman commented on HBASE-698:
-------------------------------------
Currently the master will only recover logs during startup if it finds
information in in the ROOT or META that indicate that a region was being
served. Without appends in hadoop, the edits to the ROOT or META could be lost
and so the master would not look for the log of the server that was killed.
This is not a good way to do this. Once appends make log files persistent, the
master should start up in safe mode, and first recover all the log files it
finds. Region servers will not create their logs until the master has finished
recovering all the existing logs and tells the region servers it has finished.
> 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
> Fix For: 0.3.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.
