[
https://issues.apache.org/jira/browse/HBASE-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730930#action_12730930
]
Jean-Daniel Cryans commented on HBASE-698:
------------------------------------------
@Dave
I have the same situation here and I'm doing some tests. I saw that edits going
to since deleted regions will still create a directory and put the
oldlogfile.log there. This is not so bad but not so good either, it eats up
disk space for no reason... Edits going to META are more problematic, you could
see old regions coming back and completely mess up your data. I'm currently
trying to recreate such a setup to confirm.
So, if you want to apply this patch, I currently suggest that you delete those
folders.
> 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.
