[
https://issues.apache.org/jira/browse/HBASE-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705671#action_12705671
]
Jim Kellerman commented on HBASE-698:
-------------------------------------
> Andrew Purtell added a comment - 30/Apr/09 03:28 PM
> The scope of this problem is narrowed by new developments. With multiple
> masters on
> standby and fail over via ZK, the possibility of encountering this situation
> is reduced.
Agreed that the window for missing a lease loss narrows the window greatly.
Do the standby masters watch the region server leases?
The gist of the patch I was working on was to move the code from
BaseScanner.checkAssigned
(lines 367 - 392) to a new method in HMaster that is called from HMaster.run()
*before*
HMaster.startServiceThreads is called.
> 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.
